UI/UX Design
Systematic UI/UX design skill with design system creation guides, Figma workflow patterns, accessibility audit checklists, browser-based visual audit procedures, and design-to-code handoff templates. Produces consistent, accessible, conversion-optimized interfaces.
When to Use
- Creating or extending a design system (tokens, components, patterns)
- Designing new pages, features, or user flows
- Auditing existing UI for accessibility compliance
- Preparing design specifications for developer handoff
- Setting up Figma project structure and workflows
- Reviewing existing UI via automated browser screenshots and heuristic analysis
- Reviewing UI components against heuristics and platform guidelines
When NOT to Use
- Writing page content or copy (use
content-creation skill)
- Implementing frontend code (use
Agent(frontend-engineer) role)
- Conducting SEO audits (use
/seo-review workflow)
- Writing technical documentation (use
/docs workflow)
Design System Creation
Step 1: Audit Existing UI
Before creating a design system:
- Screenshot inventory: Capture all existing screens and components
- Pattern extraction: Identify recurring colors, typography, spacing, components
- Inconsistency map: Document where the same concept is implemented differently
- Priority matrix: Rank components by frequency of use × inconsistency severity
Step 2: Define Foundations
Build from the ground up:
| Foundation |
What to Define |
Token Naming |
| Color |
Brand, semantic, neutral, overlay palettes |
color-{category}-{shade} |
| Typography |
Font families, size scale, weights, line heights |
font-{property}-{size} |
| Spacing |
Base unit (4px or 8px), scale |
spacing-{size} |
| Border radius |
Scale from none to full |
radius-{size} |
| Elevation |
Shadow levels |
shadow-{level} |
| Motion |
Duration, easing curves |
motion-{property}-{variant} |
| Breakpoints |
Viewport thresholds |
breakpoint-{name} |
Step 3: Build Components
Follow Atomic Design progression:
- Atoms: Button, Input, Label, Icon, Badge, Avatar, Checkbox, Radio, Toggle
- Molecules: Input Group, Search Bar, Card, Dropdown, Tooltip, Alert, Breadcrumb
- Organisms: Header, Footer, Sidebar, Form, Data Table, Modal, Navigation
For each component, document:
- Variants: Primary, secondary, outline, ghost, destructive
- Sizes: xs, sm, md, lg, xl
- States: Default, hover, focus, active, disabled, loading, error
- Accessibility: ARIA role, keyboard behavior, screen reader announcement
- Responsive: Behavior at each breakpoint
- Do / Don't: Usage examples and anti-patterns
Step 4: Document and Maintain
- Publish component library with live examples
- Version with semantic versioning
- Changelog for every update
- Deprecation notices with migration guides
See design-system-checklist.md for the full creation checklist.
Figma Workflow
See figma-workflow.md for detailed Figma project setup, component organization, Auto Layout patterns, and developer handoff procedures.
Quick Reference
| Figma Concept |
Code Equivalent |
| Auto Layout |
Flexbox / CSS Grid |
| Component variants |
React props / variant configs |
| Design tokens (Variables) |
CSS custom properties |
| Constraints |
CSS positioning / responsive rules |
| Component instances |
React component usage |
Accessibility Audit
See accessibility-checklist.md for the comprehensive WCAG 2.2 AA audit checklist.
Quick Audit (5-Minute Check)
- Tab through the page — can you reach and operate every interactive element?
- Zoom to 200% — does content reflow without horizontal scrolling?
- Check contrast — do all text elements meet 4.5:1 (normal) / 3:1 (large)?
- Screen reader test — do headings, landmarks, and alt text make sense?
- Keyboard-only — can you complete the primary task without a mouse?
Design-to-Code Handoff Template
When handing off designs to developers, provide:
## Component: [Name]
### Visual Spec
- Dimensions: [width × height or fluid]
- Spacing: [padding, margin in token values]
- Colors: [background, text, border in token values]
- Typography: [font, size, weight, line-height in token values]
- Border: [width, style, color, radius in token values]
- Shadow: [elevation token]
### Variants
- [variant-name]: [visual differences]
### States
- Default: [spec]
- Hover: [changes from default]
- Focus: [focus indicator spec]
- Active: [changes]
- Disabled: [opacity, cursor, interaction]
### Responsive Behavior
- Mobile (< 640px): [layout changes]
- Tablet (640–1024px): [layout changes]
- Desktop (> 1024px): [default layout]
### Interactions
- [trigger] → [animation: property, duration, easing]
### Accessibility
- Role: [ARIA role if not implicit]
- Keyboard: [key bindings]
- Screen reader: [announcement text]
### Code Reference
- Component: `<ComponentName variant="..." size="..." />`
- Tokens: `--token-name: value`
Integration
- Follows rules:
Agent(ui-ux-designer) (design principles, accessibility, design systems)
- Used by workflows:
/ui-ux-design (primary), /feature-dev (UI features)
- Companion resources:
design-system-checklist.md, figma-workflow.md, accessibility-checklist.md, visual-audit-checklist.md
1---
2name: ui-ux-design-3
3description: UI/UX design systems, Figma workflows, accessibility checklists, browser-based visual audit with automated screenshots, component specification patterns, and design-to-code handoff procedures. Use when designing interfaces, creating design systems, auditing accessibility, reviewing existing UI via browser screenshots, specifying components, or preparing design handoff for developers.
4user-invocable: true
5---
6
7# UI/UX Design
8
9Systematic UI/UX design skill with design system creation guides, Figma workflow patterns, accessibility audit checklists, browser-based visual audit procedures, and design-to-code handoff templates. Produces consistent, accessible, conversion-optimized interfaces.
10
11## When to Use
12
13- Creating or extending a design system (tokens, components, patterns)
14- Designing new pages, features, or user flows
15- Auditing existing UI for accessibility compliance
16- Preparing design specifications for developer handoff
17- Setting up Figma project structure and workflows
18- Reviewing existing UI via automated browser screenshots and heuristic analysis
19- Reviewing UI components against heuristics and platform guidelines
20
21## When NOT to Use
22
23- Writing page content or copy (use `content-creation` skill)
24- Implementing frontend code (use `Agent(frontend-engineer)` role)
25- Conducting SEO audits (use `/seo-review` workflow)
26- Writing technical documentation (use `/docs` workflow)
27
28## Design System Creation
29
30### Step 1: Audit Existing UI
31
32Before creating a design system:
33
341. **Screenshot inventory**: Capture all existing screens and components
352. **Pattern extraction**: Identify recurring colors, typography, spacing, components
363. **Inconsistency map**: Document where the same concept is implemented differently
374. **Priority matrix**: Rank components by frequency of use × inconsistency severity
38
39### Step 2: Define Foundations
40
41Build from the ground up:
42
43| Foundation | What to Define | Token Naming |
44|---|---|---|
45| **Color** | Brand, semantic, neutral, overlay palettes | `color-{category}-{shade}` |
46| **Typography** | Font families, size scale, weights, line heights | `font-{property}-{size}` |
47| **Spacing** | Base unit (4px or 8px), scale | `spacing-{size}` |
48| **Border radius** | Scale from none to full | `radius-{size}` |
49| **Elevation** | Shadow levels | `shadow-{level}` |
50| **Motion** | Duration, easing curves | `motion-{property}-{variant}` |
51| **Breakpoints** | Viewport thresholds | `breakpoint-{name}` |
52
53### Step 3: Build Components
54
55Follow Atomic Design progression:
56
571. **Atoms**: Button, Input, Label, Icon, Badge, Avatar, Checkbox, Radio, Toggle
582. **Molecules**: Input Group, Search Bar, Card, Dropdown, Tooltip, Alert, Breadcrumb
593. **Organisms**: Header, Footer, Sidebar, Form, Data Table, Modal, Navigation
60
61For each component, document:
62- **Variants**: Primary, secondary, outline, ghost, destructive
63- **Sizes**: xs, sm, md, lg, xl
64- **States**: Default, hover, focus, active, disabled, loading, error
65- **Accessibility**: ARIA role, keyboard behavior, screen reader announcement
66- **Responsive**: Behavior at each breakpoint
67- **Do / Don't**: Usage examples and anti-patterns
68
69### Step 4: Document and Maintain
70
71- Publish component library with live examples
72- Version with semantic versioning
73- Changelog for every update
74- Deprecation notices with migration guides
75
76See `design-system-checklist.md` for the full creation checklist.
77
78## Figma Workflow
79
80See `figma-workflow.md` for detailed Figma project setup, component organization, Auto Layout patterns, and developer handoff procedures.
81
82### Quick Reference
83
84| Figma Concept | Code Equivalent |
85|---|---|
86| Auto Layout | Flexbox / CSS Grid |
87| Component variants | React props / variant configs |
88| Design tokens (Variables) | CSS custom properties |
89| Constraints | CSS positioning / responsive rules |
90| Component instances | React component usage |
91
92## Accessibility Audit
93
94See `accessibility-checklist.md` for the comprehensive WCAG 2.2 AA audit checklist.
95
96### Quick Audit (5-Minute Check)
97
981. **Tab through the page** — can you reach and operate every interactive element?
992. **Zoom to 200%** — does content reflow without horizontal scrolling?
1003. **Check contrast** — do all text elements meet 4.5:1 (normal) / 3:1 (large)?
1014. **Screen reader test** — do headings, landmarks, and alt text make sense?
1025. **Keyboard-only** — can you complete the primary task without a mouse?
103
104## Design-to-Code Handoff Template
105
106When handing off designs to developers, provide:
107
108```
109## Component: [Name]
110
111### Visual Spec
112- Dimensions: [width × height or fluid]
113- Spacing: [padding, margin in token values]
114- Colors: [background, text, border in token values]
115- Typography: [font, size, weight, line-height in token values]
116- Border: [width, style, color, radius in token values]
117- Shadow: [elevation token]
118
119### Variants
120- [variant-name]: [visual differences]
121
122### States
123- Default: [spec]
124- Hover: [changes from default]
125- Focus: [focus indicator spec]
126- Active: [changes]
127- Disabled: [opacity, cursor, interaction]
128
129### Responsive Behavior
130- Mobile (< 640px): [layout changes]
131- Tablet (640–1024px): [layout changes]
132- Desktop (> 1024px): [default layout]
133
134### Interactions
135- [trigger] → [animation: property, duration, easing]
136
137### Accessibility
138- Role: [ARIA role if not implicit]
139- Keyboard: [key bindings]
140- Screen reader: [announcement text]
141
142### Code Reference
143- Component: `<ComponentName variant="..." size="..." />`
144- Tokens: `--token-name: value`
145```
146
147## Integration
148
149- **Follows rules**: `Agent(ui-ux-designer)` (design principles, accessibility, design systems)
150- **Used by workflows**: `/ui-ux-design` (primary), `/feature-dev` (UI features)
151- **Companion resources**: `design-system-checklist.md`, `figma-workflow.md`, `accessibility-checklist.md`, `visual-audit-checklist.md`
majiayu000