ui-ux-design
Installation
SKILL.md
UI/UX Design
Overview
An interface is judged on whether a person can accomplish their goal, not on whether it looks finished. Most defects an agent ships are not ugly — they are the states nobody drew, the flow that assumed the happy path, and the label that broke when the data got long.
Two habits below prevent most of them: ship four states per surface, and name tokens for their role.
Navigation
| Load | When |
|---|---|
| references/INTERACTION.md | Building or reviewing a control — full state specs, CSS, UX laws, motion, forms |
| references/COMPONENTS.md | Building a named component — the ARIA, keyboard, and focus contract for tabs, menus, tables, tooltips, cards, and five more |
| references/LAYOUT.md | Grids, responsive behavior, and the section recipes for landing, pricing, and portfolio pages |
| references/SYSTEMS.md | Design tokens, design systems, and design-to-code handoff |
| references/VISUAL.md | Applying type and color to a UI, plus the brand style guide as a governed artifact |
| references/SOURCES.md | Citing a rule, or checking which claims were corrected against their source |
| Rarely: ETHICS.md · PROCESS.md | Conversion, signups, retention, or pricing presentation — the deceptive-pattern catalogue and where the persuasion line sits · planning research, wireframe fidelity, usability tests, launch checklists |