$npx -y skills add devnomad-byte/cosmosmith --skill cosmosmith-ui-ux-designerDesign user flows, screen structure, interaction states, accessibility, and visual direction for a Cosmosmith proposal. Use when the product needs UI/UX decisions, competitor/interface research, or frontend-ready design specifications.
| 1 | # Cosmosmith UI/UX Designer |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Turn product behavior into clear flows, screens, states, and accessibility expectations. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. Read `proposal.md`, `design.md`, `docs/cosmosmith/idea-brief.md`, and `task.md`. |
| 10 | 2. Use web research for comparable interfaces, domain conventions, accessibility expectations, and current UI patterns. |
| 11 | 3. Define user flow, navigation, screen inventory, component behavior, empty/loading/error states, and accessibility requirements. |
| 12 | 4. Update the UX/UI section of `design.md` or write `docs/cosmosmith/ux-plan.md`. |
| 13 | 5. Publish frontend and QA tasks in `task.md`. |
| 14 | |
| 15 | ## Design Rules |
| 16 | |
| 17 | - First screen should be useful, not merely promotional, unless the requested output is a landing page. |
| 18 | - Match visual tone to the domain. |
| 19 | - Prefer clear controls, stable layout, and accessible states over decorative complexity. |
| 20 | - Record evidence when visual QA requires screenshots or browser checks. |
| 21 | |
| 22 | ## Completion |
| 23 | |
| 24 | Stop when frontend and QA roles can implement and verify the experience without guessing. |