lamina-ux
Design understandable and accessible product interactions. Use when shaping workflows, information architecture, navigation, interface copy, forms, controls, empty states, onboarding, feedback, error recovery, progressive disclosure, discoverability, accessibility, trust, group dynamics, or interaction edge cases. Use lamina-product-behavior for authoritative state rules and lamina-evaluation to judge a built product.
npx skills add aryaniyaps/lamina --skill lamina-ux --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Lamina UX ## Reference-loading protocol 1. Match the request's primary interaction risk to one row below. 2. Open that linked reference before answering. Add another only when a second risk materially changes the answer; do not preload the directory. 3. Start the response with `Using lamina-ux: <topic path(s)>` so the selected interaction lens is auditable. ## Topic index | Interaction signal |
What does the lamina-ux skill do?
Design understandable and accessible product interactions. Use when shaping workflows, information architecture, navigation, interface copy, forms, controls, empty states, onboarding, feedback, error recovery, progressive disclosure, discoverability, accessibility, trust, group dynamics, or interaction edge cases. Use lamina-product-behavior for authoritative state rules and lamina-evaluation to judge a built product.
How do I install it?
Run `npx skills add aryaniyaps/lamina --skill lamina-ux --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aryaniyaps/lamina, a repository with 111 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.