UI/UX Design
Create functional, accessible, visually distinctive interfaces. Output is working code.
When to Use
Activate automatically when:
- User requests UI components, pages, or applications
- User mentions forms, dashboards, landing pages, modals
- User asks to "design", "build", or "create" any interface
- User wants to improve existing UI/UX
Workflow
Step 1: Assess Context
Before coding, identify (internal reasoning):
- Problem being solved
- Target users
- Aesthetic direction (see REFERENCES.md)
- Constraints (framework, brand, accessibility level)
Step 2: Consult References
Fetch implementation values from REFERENCES.md:
- Color palette (with WCAG-compliant values)
- Font pairing
- Component patterns (button, input, card, etc.)
- Spacing and typography tokens
Step 3: Generate Code
Produce working implementation with:
- All interactive states (hover, focus, active, disabled, loading, error)
- Semantic HTML (button, nav, main—not div soup)
- Mobile-first responsive design
- CSS variables for maintainability
Step 4: Verify
Run through checklist before delivering.
Output Requirements
| Requirement |
Standard |
| Contrast |
4.5:1 text, 3:1 UI components |
| Focus states |
Visible outline on all interactive elements |
| Touch targets |
Minimum 44×44px |
| Reduced motion |
Respect prefers-reduced-motion |
| Labels |
All inputs have associated labels |
| Empty states |
Helpful message + clear action |
| Error states |
Explain what happened + how to fix |
Aesthetic Directions
Match to context. See REFERENCES.md for characteristics.
| Style |
Best For |
| Minimalism |
Productivity, professional, portfolios |
| Glassmorphism |
Dashboards, tech products |
| Neubrutalism |
Creative, startups, distinctive brands |
| Editorial |
Content sites, publications |
| Organic |
Consumer apps, wellness, community |
| Dark Mode |
User preference, low-light contexts |
Anti-Patterns
Avoid these markers of generic AI output:
- Purple/blue gradients on white
- Inter/Roboto/system fonts everywhere
- Cookie-cutter card layouts
- Rounded rectangles with soft shadows on everything
- Color-only meaning (no icons/text backup)
- Removed focus outlines
- Error messages without solutions
Checklist
Copy and track:
- [ ] Context assessed (problem, users, aesthetic direction)
- [ ] REFERENCES.md consulted for palette + fonts
- [ ] All interactive states implemented
- [ ] Loading and error states included
- [ ] Contrast meets WCAG AA
- [ ] Semantic HTML used
- [ ] Focus states visible
- [ ] Form inputs labeled
- [ ] prefers-reduced-motion respected
- [ ] Responsive breakpoints tested
- [ ] Empty states handled
Recovery
| Issue |
Action |
| User dislikes direction |
Propose 2-3 alternatives from Aesthetic Directions |
| Looks too generic |
Check Anti-Patterns, apply distinctive typography |
| Accessibility concerns |
Verify contrast, focus states, semantic HTML |
| States incomplete |
Walk through checklist systematically |
License: MIT - See LICENSE for complete terms
Author: Arvind Menon
1---2name: ui-ux-design-53description: Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work.4---5
6# UI/UX Design
7
8Create functional, accessible, visually distinctive interfaces. Output is working code.
9
10## When to Use
11
12**Activate automatically when:**
13
14- User requests UI components, pages, or applications
15- User mentions forms, dashboards, landing pages, modals
16- User asks to "design", "build", or "create" any interface
17- User wants to improve existing UI/UX
18
19## Workflow
20
21### Step 1: Assess Context
22
23Before coding, identify (internal reasoning):
24
25- Problem being solved
26- Target users
27- Aesthetic direction (see [REFERENCES.md](REFERENCES.md#aesthetic-directions))
28- Constraints (framework, brand, accessibility level)
29
30### Step 2: Consult References
31
32Fetch implementation values from [REFERENCES.md](REFERENCES.md):
33
34- Color palette (with WCAG-compliant values)
35- Font pairing
36- Component patterns (button, input, card, etc.)
37- Spacing and typography tokens
38
39### Step 3: Generate Code
40
41Produce working implementation with:
42
43- All interactive states (hover, focus, active, disabled, loading, error)
44- Semantic HTML (button, nav, main—not div soup)
45- Mobile-first responsive design
46- CSS variables for maintainability
47
48### Step 4: Verify
49
50Run through checklist before delivering.
51
52## Output Requirements
53
54| Requirement | Standard |
55|-------------|----------|
56| Contrast | 4.5:1 text, 3:1 UI components |
57| Focus states | Visible outline on all interactive elements |
58| Touch targets | Minimum 44×44px |
59| Reduced motion | Respect `prefers-reduced-motion` |
60| Labels | All inputs have associated labels |
61| Empty states | Helpful message + clear action |
62| Error states | Explain what happened + how to fix |
63
64## Aesthetic Directions
65
66Match to context. See [REFERENCES.md](REFERENCES.md#aesthetic-directions) for characteristics.
67
68| Style | Best For |
69|-------|----------|
70| Minimalism | Productivity, professional, portfolios |
71| Glassmorphism | Dashboards, tech products |
72| Neubrutalism | Creative, startups, distinctive brands |
73| Editorial | Content sites, publications |
74| Organic | Consumer apps, wellness, community |
75| Dark Mode | User preference, low-light contexts |
76
77## Anti-Patterns
78
79Avoid these markers of generic AI output:
80
81- Purple/blue gradients on white
82- Inter/Roboto/system fonts everywhere
83- Cookie-cutter card layouts
84- Rounded rectangles with soft shadows on everything
85- Color-only meaning (no icons/text backup)
86- Removed focus outlines
87- Error messages without solutions
88
89## Checklist
90
91Copy and track:
92
93```
94- [ ] Context assessed (problem, users, aesthetic direction)
95- [ ] REFERENCES.md consulted for palette + fonts
96- [ ] All interactive states implemented
97- [ ] Loading and error states included
98- [ ] Contrast meets WCAG AA
99- [ ] Semantic HTML used
100- [ ] Focus states visible
101- [ ] Form inputs labeled
102- [ ] prefers-reduced-motion respected
103- [ ] Responsive breakpoints tested
104- [ ] Empty states handled
105```
106
107## Recovery
108
109| Issue | Action |
110|-------|--------|
111| User dislikes direction | Propose 2-3 alternatives from Aesthetic Directions |
112| Looks too generic | Check Anti-Patterns, apply distinctive typography |
113| Accessibility concerns | Verify contrast, focus states, semantic HTML |
114| States incomplete | Walk through checklist systematically |
115
116---
117
118> **License:** MIT - See LICENSE for complete terms
119> **Author:** Arvind Menon
majiayu000