ux
Installation
SKILL.md
UX
Infer direction from the request — never ask which mode:
- Audit an existing surface → usability flow, accessibility/WCAG, form, navigation/IA, or error-recovery pass. Load
references/auditing.md. - Design or build UI → screen, dashboard, prototype, design system, deck, or motion; the anti-slop polish pass; or elevate a whole working app to feel premium (craft, rationed signature moments, retention loops under an ethics gate). Load
references/crafting.md. - Artifact lives inside an embedding host (tweak panel, direct edit, speaker notes, export)? Also load
references/host-integration.md. - Before calling a built artifact done, run
references/browser-verification.md— reading source is not seeing the render.
Core principle: the next correct action must be visible, reversible, and accessible. Audits find where it isn't; new UI is designed so it is — context before craft: read the product, existing system, and assets before inventing visuals.
Invariants
- WCAG is the floor, not the ceiling — passing a checker does not make a flow usable. Automated scanners catch only a minority of failures: keyboard path, focus order, semantics, contrast at zoom, and assistive-tech behavior need human checks, so every accessibility finding separates likely WCAG failures from issues needing manual verification and carries a manual-verify note.
- Anti-slop bar. Generated UI that could have come from a generic AI template is not done. One stock trope may be intentional; three means restart. Name the committed direction — material, type voice, accent, density — in the handoff.
- Honest content. No fabricated metrics, logos, or testimonials — explicit placeholders instead. Never silently invent a design-system component. Respect
prefers-reduced-motion. No dark-pattern retention mechanics (streak-shaming, fake urgency); don't clone an identifiable brand's UI or visual identity — extract principles into an original design.