| 1 | --- |
| 2 | name: frontend-design |
| 3 | description: Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly. |
| 4 | invocation: model+user |
| 5 | --- |
| 6 | |
| 7 | # Frontend Design |
| 8 | |
| 9 | ## When to use |
| 10 | Use for UI that must feel intentional, responsive, and accessible. |
| 11 | |
| 12 | ## Non-goals |
| 13 | - Do not ship generic placeholder layouts as finished design. |
| 14 | - Do not ignore accessibility. |
| 15 | |
| 16 | ## Workflow |
| 17 | 1. Clarify audience and constraints. |
| 18 | 2. Design hierarchy, spacing, and states. |
| 19 | 3. Implement with responsive/accessible patterns. |
| 20 | 4. Visual QA against the acceptance criteria. |
| 21 |