UX Designer
Overview
Designs intuitive, accessible user experiences grounded in research rather than personal preference. Covers a 5-phase design process from information architecture through developer handoff, including user flows, wireframing, prototyping, usability testing, and accessibility compliance.
When to use: Creating user journeys and flows, designing wireframes and prototypes, improving usability, building design systems, conducting accessibility audits, preparing developer handoff documentation.
When NOT to use: Backend architecture without UI, database schema design, DevOps configuration.
Quick Reference
| Phase |
Goal |
Key Deliverables |
| Information Architecture |
Organize content and functionality |
Site map, navigation design, labeling taxonomy |
| User Flows |
Map paths users take to complete tasks |
Flow diagrams, happy path, error states, edge cases |
| Wireframing |
Create low-fidelity layouts |
Lo-fi/mid-fi/hi-fi wireframes, layout patterns |
| Prototyping and Testing |
Create interactive prototypes and test |
Clickable prototype, usability test results |
| UI Design and Handoff |
Production-ready designs |
Design specs, component states, responsive layouts |
Key UX Principles
- Consistency -- use familiar patterns; do not reinvent standard UI elements
- Feedback -- confirm user actions with success messages and loading states
- Error Prevention -- design to prevent errors, not just handle them
- Recognition Over Recall -- show options rather than requiring memory
- Flexibility -- support both novice and expert users with shortcuts and defaults
Design Patterns Summary
| Pattern |
Key Rules |
| Forms |
Label above field, inline validation, one column, group related fields |
| Navigation |
Current page highlighted, breadcrumbs for depth, max 7 top nav items |
| Empty States |
Explain why empty, provide clear next action, use illustration or icon |
| Loading States |
Skeleton screens over spinners, progress indicators, optimistic UI |
Common Mistakes
| Mistake |
Correct Pattern |
| Designing based on personal preference instead of user research |
Ground every design decision in user research, card sorting, or usability test data |
| Skipping empty, loading, and error state designs |
Design all states for every screen: default, loading, empty, error, and success |
| Using placeholder text as form labels |
Place labels above fields; placeholders disappear on input and fail accessibility |
| Ignoring keyboard navigation and focus states |
Test Tab order, visible focus indicators, and ARIA labels for all interactive elements |
| Designing a single layout for all screen sizes |
Create separate responsive layouts for mobile, tablet, and desktop breakpoints |
| Not testing with real users before development |
Conduct usability testing with 5+ participants on interactive prototypes |
Delegation
- User research and testing: Use
Task agent to plan card sorting, tree testing, and usability test sessions
- Accessibility audit: Use
Explore agent to verify WCAG 2.2 AA compliance across all screens using automated tools
- Design system architecture: Use
Plan agent to define color scales, typography hierarchy, spacing grid, and component library structure
References
- Design Process -- 5-phase UX process, information architecture, user flows, wireframing, prototyping, and handoff
- Visual Design Fundamentals -- color theory, typography scales, spacing systems, visual hierarchy, dark mode, and responsive patterns
- Accessibility Guide -- WCAG 2.2 AA compliance, keyboard navigation, screen readers, color contrast, and audit checklists
- Tools and Resources -- design tools, prototyping platforms, testing services, and accessibility checkers
1---2name: ux-designer3description: Designs user experiences and interfaces grounded in research. Use when creating user journeys, wireframes, prototypes, or improving usability. Use for information architecture, interaction design, accessibility audits, design system creation, and developer handoff.4license: MIT5---6
7# UX Designer
8
9## Overview
10
11Designs intuitive, accessible user experiences grounded in research rather than personal preference. Covers a 5-phase design process from information architecture through developer handoff, including user flows, wireframing, prototyping, usability testing, and accessibility compliance.
12
13**When to use:** Creating user journeys and flows, designing wireframes and prototypes, improving usability, building design systems, conducting accessibility audits, preparing developer handoff documentation.
14
15**When NOT to use:** Backend architecture without UI, database schema design, DevOps configuration.
16
17## Quick Reference
18
19| Phase | Goal | Key Deliverables |
20| ------------------------ | -------------------------------------- | --------------------------------------------------- |
21| Information Architecture | Organize content and functionality | Site map, navigation design, labeling taxonomy |
22| User Flows | Map paths users take to complete tasks | Flow diagrams, happy path, error states, edge cases |
23| Wireframing | Create low-fidelity layouts | Lo-fi/mid-fi/hi-fi wireframes, layout patterns |
24| Prototyping and Testing | Create interactive prototypes and test | Clickable prototype, usability test results |
25| UI Design and Handoff | Production-ready designs | Design specs, component states, responsive layouts |
26
27## Key UX Principles
28
291. **Consistency** -- use familiar patterns; do not reinvent standard UI elements
302. **Feedback** -- confirm user actions with success messages and loading states
313. **Error Prevention** -- design to prevent errors, not just handle them
324. **Recognition Over Recall** -- show options rather than requiring memory
335. **Flexibility** -- support both novice and expert users with shortcuts and defaults
34
35## Design Patterns Summary
36
37| Pattern | Key Rules |
38| -------------- | ---------------------------------------------------------------------- |
39| Forms | Label above field, inline validation, one column, group related fields |
40| Navigation | Current page highlighted, breadcrumbs for depth, max 7 top nav items |
41| Empty States | Explain why empty, provide clear next action, use illustration or icon |
42| Loading States | Skeleton screens over spinners, progress indicators, optimistic UI |
43
44## Common Mistakes
45
46| Mistake | Correct Pattern |
47| --------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
48| Designing based on personal preference instead of user research | Ground every design decision in user research, card sorting, or usability test data |
49| Skipping empty, loading, and error state designs | Design all states for every screen: default, loading, empty, error, and success |
50| Using placeholder text as form labels | Place labels above fields; placeholders disappear on input and fail accessibility |
51| Ignoring keyboard navigation and focus states | Test Tab order, visible focus indicators, and ARIA labels for all interactive elements |
52| Designing a single layout for all screen sizes | Create separate responsive layouts for mobile, tablet, and desktop breakpoints |
53| Not testing with real users before development | Conduct usability testing with 5+ participants on interactive prototypes |
54
55## Delegation
56
57- **User research and testing**: Use `Task` agent to plan card sorting, tree testing, and usability test sessions
58- **Accessibility audit**: Use `Explore` agent to verify WCAG 2.2 AA compliance across all screens using automated tools
59- **Design system architecture**: Use `Plan` agent to define color scales, typography hierarchy, spacing grid, and component library structure
60
61## References
62
63- [Design Process](references/design-process.md) -- 5-phase UX process, information architecture, user flows, wireframing, prototyping, and handoff
64- [Visual Design Fundamentals](references/visual-design.md) -- color theory, typography scales, spacing systems, visual hierarchy, dark mode, and responsive patterns
65- [Accessibility Guide](references/accessibility-guide.md) -- WCAG 2.2 AA compliance, keyboard navigation, screen readers, color contrast, and audit checklists
66- [Tools and Resources](references/tools-and-resources.md) -- design tools, prototyping platforms, testing services, and accessibility checkers
oakoss