Executes the UX Design Creation workflow as the UX Designer.
Workflow Overview#
Goal: Create comprehensive UX design with wireframes, user flows, and accessibility
Phase: Phase 2 (Planning) or Phase 3 (Solutioning)
Agent: UX Designer
Inputs: Requirements (PRD/tech-spec), user stories, target platforms
Output: UX design document with wireframes, flows, accessibility annotations, developer handoff
Duration: 60-120 minutes
Pre-Flight#
- Load context per
helpers.md#Combined-Config-Load -
Load requirements per
helpers.md#Load-Documents- Look for PRD (
prd.md) or tech-spec (tech-spec.md) - Extract user stories, acceptance criteria, NFRs
- Look for PRD (
-
Explain purpose:
"I'll create a comprehensive UX design for your project. This includes user flows, wireframes, accessibility annotations, and developer handoff documentation."
UX Design Process#
Use TodoWrite to track: Load Requirements â Define Scope â Create User Flows â Design Wireframes â Ensure Accessibility â Document Components â Generate Design Doc â Validate â Update Status
Part 1: Analyze Requirements#
Load requirements document:
Per helpers.md#Load-Documents:
- Read PRD or tech-spec from project
- Extract all user stories (US-XXX)
-
Extract all NFRs related to UX:
- Performance (page load times)
- Usability (ease of use, learnability)
- Accessibility (WCAG level)
- Compatibility (browsers, devices)
Ask user for additional context:
Q1: Target Platforms
"What platforms are we designing for?"
Options (select multiple):
- Web (desktop)
- Web (mobile)
- Web (tablet)
- iOS native
- Android native
- Progressive Web App (PWA)
Store as: {{target_platforms}}
Q2: Design Complexity
"What level of design detail?"
- High-level - User flows and basic wireframes
- Detailed - Full wireframes with interactions
- Comprehensive - Wireframes, interactions, component specs, design system
Store as: {{design_level}}
Q3: Accessibility Requirements
"What accessibility level?"
- WCAG 2.1 Level A (minimum)
- WCAG 2.1 Level AA (recommended)
- WCAG 2.1 Level AAA (highest)
Store as: {{wcag_level}}
Q4: Existing Design System
"Do you have an existing design system or brand guidelines?"
If yes: Ask for link or file If no: Will create basic design tokens
Store as: {{design_system_url}}
Part 2: Identify Design Scope#
From requirements, extract screens to design:
Group user stories by screen/flow:
Flow 1: User Authentication
- US-001: User can sign up
- US-002: User can log in
- US-003: User can reset password
Screens needed: Sign up, Login, Forgot password
Flow 2: Dashboard
- US-004: User can view dashboard
- US-005: User can filter data
Screens needed: Dashboard (empty state), Dashboard (with data)
[Continue for all user stories...]
Count total screens: {{screen_count}}
Inform user:
"I've identified {{screen_count}} screens across {{flow_count}} user flows."
Part 3: Create User Flows#
For each major flow, create user flow diagram.
User flow format:
### Flow: { { flow_name } }
**Entry Point:** { { how_user_starts_flow } }
**Happy Path:**
1. { { screen_1 } } â User { { action } } â { { screen_2 } }
2. { { screen_2 } } â User { { action } } â { { screen_3 } }
3. { { screen_3 } } â { { final_state } }
**Decision Points:**
- At { { screen } } : If { { condition } } â { { alternative_path } }
**Error Cases:**
- { { error_scenario } } â Show { { error_message } } â { { recovery_action } }
**Exit Points:**
- Success: { { success_screen } }
- Cancel: { { cancel_destination } }
- Error: { { error_screen } }
**Diagram:**
[Start] â [Screen 1: {{name}}] â {{action}} [Screen 2: {{name}}] â {{action}} âââ [Success: {{screen}}] âââ [Error: {{screen}}]
Create flows for:
- Authentication flows
- Core feature flows
- Settings/configuration flows
- Error handling flows
Typical count: 3-10 flows depending on project complexity
Part 3.5: Design Tool Selection (Optional)#
Check for available MCP design tools and offer integration:
Q: Would you like to use a design tool?
If MCP design tools are configured, they can be utilized for wireframe and design work.
- Figma - Cloud-based design (MCP:
figma)- Pencil - Local design, Git-trackable (MCP:
pencil)- ASCII/Markdown - No tools required (default)
Store as: {{design_tool}}
Tool detection: Check availability via MCP server connection status. Auto-select option 3 (ASCII/Markdown) if not detected.
When Figma is selected ({{design_tool}} = figma)
Workflow using MCP tools:
-
Reference existing designs: Load existing design context from Figma files with
get_design_context -
Check design variables: Extract design system variables/styles with
get_variable_defs -
Check code mapping: Verify Figma-to-code component mapping with
get_code_connect_map -
Create design: Generate wireframes/designs in Figma with
generate_figma_design(if supported) -
User flow diagrams: Generate Mermaid to FigJam diagrams with
generate_diagram - Check screenshot: Preview results with
get_screenshot -
Design system rules: Document design system rules with
create_design_system_rules
Figma limitations:
- Be mindful of rate limits (Starter = 6/month, Dev/Full = per-minute limits)
generate_figma_designis only supported by some clients (rolling out)- Cloud-based so offline unavailable
- Falls back to ASCII/Markdown when not supported
When Pencil is selected ({{design_tool}} = pencil)
Workflow using MCP tools:
- Reference existing designs: Read .pen file hierarchy with
batch_get - Check editor state: Get current editing state with
get_editor_state -
Create wireframes: Create/modify elements with
batch_design(batch processing) -
Sync design tokens: Read/set design tokens with
get_variables/set_variables - Analyze layout: Analyze layout structure with
snapshot_layout - Check results: Preview screenshot with
get_screenshot
Pencil advantages:
.penfiles can be Git-tracked in the same repository as code- Fully local execution, no cloud transfer (privacy)
- Offline work possible
Pencil limitations:
- Pencil desktop app must be running
- CLI is still experimental
- Falls back to ASCII/Markdown when not running
When ASCII/Markdown is selected (default)
Proceed with the conventional approach without MCP tools. Use Option 1 (ASCII Art) or Option 2 (Structured Description) from Part 4 below.
Part 4: Design Wireframes#
For each screen, create wireframe.
Wireframe approaches:
Option 1: ASCII Art (quick visualization)
Screen: { { screen_name } }
Mobile (320-767px):
âââââââââââââââââââââââ
â â° Logo [?] â â Header (60px)
âââââââââââââââââââââââĪ
â â
â Page Title â â H1 (32px)
â Subtitle â â H2 (18px)
â â
â âââââââââââââââââ â
â â Card 1 â â â Card (full-width)
â â Title â â
â â Description â â
â â [Button] â â
â âââââââââââââââââ â
â â
â âââââââââââââââââ â
â â Card 2 â â
â âââââââââââââââââ â
â â
â [Primary CTA] â â Button (48px height)
â â
âââââââââââââââââââââââ
Desktop (1024px+):
âââââââââââââââââââââââââââââââââââââââââââ
â Logo Nav1 Nav2 Nav3 [?] â â Header
âââââââââââââââââââââââââââââââââââââââââââĪ
â â
â Page Title Subtitle â
â â
â ââââââââââââ ââââââââââââ â
â â Card 1 â â Card 2 â â â 2-column grid
â â â â â â
â â [Button] â â [Button] â â
â ââââââââââââ ââââââââââââ â
â â
â [Primary CTA] â
â â
âââââââââââââââââââââââââââââââââââââââââââ
Option 2: Structured Description (detailed specs)
### Screen: { { screen_name } }
**Purpose:** { { what_user_does_here } }
**Layout Structure:**
**Header (fixed, 60px height):**
- Logo (left, 40px à 40px)
- Click â Home page
- Navigation menu (center)
- Nav Item 1, Nav Item 2, Nav Item 3
- Active state: underline
- Help icon (right, 24px à 24px)
- Click â Help modal
**Main Content (scrollable):**
**Hero Section (full-width, 400px height):**
- Headline (H1, 48px, center-aligned)
- Subheadline (H2, 24px, center-aligned)
- Background: gradient or image
**Card Grid (responsive):**
- Layout: 2 columns (desktop), 1 column (mobile)
- Gap: 24px between cards
**Card Component (300px à 250px):**
- Image (full-width, 150px height)
- Title (H3, 20px, 16px padding)
- Description (Body text, 14px, 16px padding)
- CTA Button (bottom, 16px padding)
- Primary style
- Full-width on mobile
- Fixed-width on desktop (160px)
**CTA Section (center-aligned, 200px height):**
- Primary Button (200px à 56px)
- Text: " { { cta_text } } "
- Click â { { destination } }
**Footer (full-width, 120px height):**
- Links (horizontal, center-aligned)
- Copyright notice (center, 12px text)
**Interactions:**
- Card hover â Elevation shadow
- Button hover â Darken 10%
- Button click â { { action } }
- Links hover â Underline
**States:**
- Default
- Hover (for interactive elements)
- Focus (keyboard navigation)
- Active (click/tap)
- Disabled (when applicable)
- Loading (for async actions)
**Responsive Behavior:**
- **Mobile (320-767px):**
- Single column layout
- Stack cards vertically
- Full-width buttons
- Hamburger menu for navigation
- **Tablet (768-1023px):**
- 2-column grid
- Navigation visible
- Moderate padding
- **Desktop (1024px+):**
- 2-3 column grid
- Maximum content width: 1200px
- Centered with side margins
Create wireframes for all {{screen_count}} screens.
Part 5: Ensure Accessibility#
For each screen, document accessibility features:
### Accessibility: { { screen_name } }
**WCAG { { wcag_level } } Compliance:**
**Perceivable:**
- [ ] All images have alt text: " { { alt_text } } "
- [ ] Color contrast checked:
- Text on background: { { ratio } } (minimum 4.5:1)
- UI components: { { ratio } } (minimum 3:1)
- [ ] Information not conveyed by color alone
- [ ] Text resizable to 200% without breaking layout
- [ ] No horizontal scrolling at 320px width
**Operable:**
- [ ] Tab order: { { tab_order_sequence } }
- [ ] Focus indicators visible (2px outline, primary color)
- [ ] No keyboard traps
- [ ] Skip navigation link: " Skip to main content "
- [ ] Touch targets minimum 44px à 44px
- [ ] Animations respect prefers-reduced-motion
**Understandable:**
- [ ] Page language: `lang= " en " `
- [ ] Form labels for all inputs
- [ ] Error messages: " { { example_error } } " (clear and actionable)
- [ ] Consistent navigation across pages
- [ ] Predictable interactions (no surprise navigation)
**Robust:**
- [ ] Semantic HTML: ` < header > `, ` < nav > `, ` < main > `, ` < footer > `
- [ ] ARIA labels where needed:
- Button: `aria-label= " { { label } } " `
- Icon-only: `aria-label= " { { description } } " `
- [ ] Form validation: `aria-invalid`, `aria-describedby`
- [ ] Modal: `role= " dialog " `, `aria-modal= " true " `
**Keyboard Navigation:**
Tab â Focus next interactive element Shift+Tab â Focus previous Enter â Activate button/link Space â Activate button, toggle checkbox Escape â Close modal/dropdown Arrow keys â Navigate within component (tabs, menus)
**Screen Reader Annotations:**
- Landmark regions: header, nav, main, footer
- Headings hierarchy: H1 (once), H2 (sections), H3 (subsections)
- Alternative text for images: descriptive, not decorative
- Live regions for dynamic content: `aria-live= " polite " `
Part 6: Define Components#
Extract reusable components from wireframes:
## Component Library
### Button Component
**Variants:**
- **Primary:** Main actions (e.g., Submit, Save)
- Background: Primary color
- Text: White
- Padding: 12px 24px
- Border-radius: 4px
- Font: 16px, 600 weight
- **Secondary:** Less important actions (e.g., Cancel)
- Background: Transparent
- Text: Primary color
- Border: 1px solid primary
- Padding: 12px 24px
- **Tertiary:** Minimal emphasis (e.g., text links)
- Background: Transparent
- Text: Primary color
- No border
**States:**
- Default
- Hover: Background darkens 10%
- Focus: 2px outline, offset 2px
- Active: Background darkens 20%
- Disabled: Opacity 50%, cursor not-allowed
**Accessibility:**
- Minimum size: 44px à 44px
- Focus indicator visible
- aria-disabled when disabled
---
### Card Component
**Structure:**
- Image (optional, 16:9 aspect ratio)
- Title (H3)
- Description (Body text)
- Action button (optional)
**Sizing:**
- Mobile: Full-width
- Tablet: 48% width (2 columns)
- Desktop: 32% width (3 columns)
**Spacing:**
- Internal padding: 16px
- Gap between cards: 24px
**States:**
- Default: elevation 1
- Hover: elevation 2
- Focus: outline
---
### Form Input Component
**Structure:**
- Label (above input, required)
- Input field
- Help text (optional)
- Error message (when invalid)
**Styling:**
- Border: 1px solid neutral-300
- Padding: 12px
- Border-radius: 4px
- Font: 16px (prevent zoom on mobile)
**States:**
- Default: neutral border
- Focus: primary border, 2px
- Error: error border, show error message
- Disabled: gray background, not-allowed cursor
**Accessibility:**
- Label linked to input: `for= " { { id } } " `
- Required: `aria-required= " true " `
- Error: `aria-invalid= " true " `, `aria-describedby= " { { error-id } } " `
[Define all reusable components...]
Part 7: Define Design Tokens#
Create design system tokens:
## Design Tokens
### Colors
**Primary Palette:**
- Primary: #0066CC (contrast ratio: 4.57:1 on white)
- Primary-dark: #004C99
- Primary-light: #3385D6
**Semantic Colors:**
- Success: #00AA44 (WCAG AA compliant)
- Warning: #FF8800
- Error: #DD0000
- Info: #0066CC
**Neutral Palette:**
- Neutral-50: #F9F9F9 (backgrounds)
- Neutral-100: #F0F0F0
- Neutral-300: #CCCCCC (borders)
- Neutral-500: #999999 (secondary text)
- Neutral-700: #555555 (primary text)
- Neutral-900: #222222 (headings)
**Contrast Ratios (checked):**
- Neutral-700 on white: 7.5:1 â (AAA)
- Primary on white: 4.57:1 â (AA)
- Error on white: 6.2:1 â (AA)
### Typography
**Font Family:**
- Primary: -apple-system, BlinkMacSystemFont, " Segoe UI " , Roboto, sans-serif
- Monospace: " SF Mono " , Monaco, monospace
**Type Scale:**
- H1: 48px / 600 / 1.2 line-height
- H2: 36px / 600 / 1.3
- H3: 24px / 600 / 1.4
- H4: 20px / 600 / 1.4
- Body: 16px / 400 / 1.6
- Small: 14px / 400 / 1.5
- Tiny: 12px / 400 / 1.4
**Responsive Type:**
- Mobile: Reduce by 20%
- Tablet: Reduce by 10%
- Desktop: Base scale
### Spacing
**Scale (based on 8px):**
- xs: 4px
- sm: 8px
- md: 16px
- lg: 24px
- xl: 32px
- 2xl: 48px
- 3xl: 64px
**Layout:**
- Container max-width: 1200px
- Gutter: 16px (mobile), 24px (desktop)
- Section spacing: 48px (mobile), 96px (desktop)
### Shadows
**Elevation:**
- Level 1: 0 1px 3px rgba(0,0,0,0.12)
- Level 2: 0 4px 6px rgba(0,0,0,0.16)
- Level 3: 0 10px 20px rgba(0,0,0,0.20)
### Border Radius
- Small: 4px (buttons, inputs)
- Medium: 8px (cards)
- Large: 16px (modals)
- Circle: 50% (avatars, icon buttons)
### Breakpoints
- Mobile: 320px - 767px
- Tablet: 768px - 1023px
- Desktop: 1024px+
Part 8: Create Developer Handoff#
Document implementation details:
## Developer Handoff
### Implementation Priorities
**Phase 1 - Foundation:**
1. Set up design tokens (colors, spacing, typography)
2. Implement base components (Button, Input, Card)
3. Create responsive grid system
4. Set up accessibility infrastructure
**Phase 2 - Screens:**
1. { { highest_priority_screen } }
2. { { second_priority_screen } }
3. { { third_priority_screen } }
**Phase 3 - Polish:**
1. Animations and transitions
2. Loading states
3. Error states
4. Edge cases
### Component Implementation Notes
**Button Component:**
/* Base button */ .btn { padding: 12px 24px; border-radius: 4px; font-size: 16px; font-weight: 600; min-width: 44px; min-height: 44px; cursor: pointer; transition: background 0.2s; }
.btn:focus { outline: 2px solid var(--primary); outline-offset: 2px; }
/* Primary variant */ .btn-primary { background: var(--primary); color: white; }
.btn-primary:hover { background: var(--primary-dark); }
### Responsive Implementation
**Mobile-first approach:**
/* Base (mobile) */ .container { padding: 16px; }
/* Tablet */ @media (min-width: 768px) { .container { padding: 24px; } }
/* Desktop */ @media (min-width: 1024px) { .container { max-width: 1200px; margin: 0 auto; } }
### Accessibility Implementation
**Required attributes:**
- All images: `alt= " { { description } } " `
- Form inputs: `id`, `aria-label` or ` < label for > `
- Buttons: `aria-label` if icon-only
- Modals: `role= " dialog " `, `aria-modal= " true " `
- Live regions: `aria-live= " polite " `
**Testing:**
- Keyboard navigation (Tab, Enter, Escape)
- Screen reader (test with NVDA/JAWS/VoiceOver)
- Color contrast (use Axe DevTools)
- Zoom to 200% (check layout)
### Assets Needed
**Images:**
- Logo (SVG preferred, PNG fallback)
- Icons (SVG, 24px à 24px)
- Placeholder images (16:9 ratio)
**Fonts:**
- System fonts (no web fonts for performance)
**Third-party:**
- None (using native HTML/CSS/JS)
Part 9: Generate UX Design Document#
Create comprehensive design document per helpers.md#Apply-Variables-to-Template
Use template: ux-design.md (or generate inline)
Document structure:
# UX Design: { { project_name } }
**Date:** { { date } }
**Designer:** { { user_name } }
**Version:** 1.0
## Project Overview
**Project:** { { project_name } }
**Target Platforms:** { { target_platforms } }
**Accessibility:** WCAG { { wcag_level } }
## Design Scope
**Screens:** { { screen_count } }
**User Flows:** { { flow_count } }
**Components:** { { component_count } }
## User Flows
{ { all_flows_from_part_3 } }
## Wireframes
{ { all_wireframes_from_part_4 } }
## Accessibility
{ { accessibility_annotations_from_part_5 } }
## Component Library
{ { components_from_part_6 } }
## Design Tokens
{ { design_tokens_from_part_7 } }
## Developer Handoff
{ { handoff_from_part_8 } }
## Validation
**Requirements Coverage:**
- [ ] US-001: { { requirement } } â { { screen } }
- [ ] US-002: { { requirement } } â { { screen } }
[All user stories mapped to screens]
**Accessibility Checklist:**
- [ ] WCAG { { level } } compliance verified
- [ ] Keyboard navigation tested
- [ ] Screen reader compatible
- [ ] Color contrast verified
- [ ] Responsive on all target platforms
**Sign-off:**
- [ ] Product Manager approved
- [ ] System Architect reviewed
- [ ] Ready for implementation
---
*Generated by BMAD Method v6 - UX Designer*
*Design Date: { { date } } *
Save to: {{output_folder}}/ux-design-{{project_name}}.md
Inform user:
â UX Design Complete!
Screens: { { screen_count } }
User Flows: { { flow_count } }
Components: { { component_count } }
Accessibility: WCAG { { level } }
Document: { { file_path } }
Ready for developer handoff!
Update Status#
Per helpers.md#Update-Workflow-Status
Update bmm-workflow-status.yaml:
phase_2_planning:
ux_design_completed: true
ux_design_date: { { current_date } }
screens_designed: { { screen_count } }
accessibility_level: { { wcag_level } }
last_workflow: create-ux-design
last_workflow_date: { { current_date } }
Recommend Next Steps#
â UX Design Complete!
Next Steps:
1. **Review with Product Manager**
- Validate designs meet requirements
- Confirm all user stories covered
- Approve design direction
2. **Architecture Review**
Run: /architecture
- Architect should validate UX constraints
- Ensure feasibility
- Identify technical considerations
3. **Implementation Planning**
Run: /sprint-planning
- Break design into implementation stories
- Prioritize screens
- Estimate effort
4. **Begin Development**
Run: /dev-story
- Start with highest-priority screen
- Implement design system tokens first
- Build components before screens
Helper References#
- Load config:
helpers.md#Combined-Config-Load - Load documents:
helpers.md#Load-Documents - Apply template:
helpers.md#Apply-Variables-to-Template - Save document:
helpers.md#Save-Output-Document - Update status:
helpers.md#Update-Workflow-Status - Determine next:
helpers.md#Determine-Next-Workflow
Notes for LLMs#
- Use TodoWrite to track UX design steps (10 steps when including Part 3.5)
- Load requirements (PRD/tech-spec) before starting
- Select design tools in Part 3.5, and branch to the appropriate workflow based on MCP server detection results
- Create user flows for all major features
- Use ASCII art for quick wireframes or structured descriptions for detailed specs
- Even when using Figma/Pencil MCP, generate ASCII/Markdown documents in parallel (for fallback and Git tracking)
- Always include accessibility annotations for WCAG compliance
- Define design tokens for consistency
- Extract reusable components
- Provide detailed developer handoff notes
- Map all user stories to screens
- Design mobile-first, then scale up
- Check color contrast ratios
- Specify all interaction states (default, hover, focus, active, disabled)
- Document responsive behavior for all breakpoints
- Use semantic HTML in recommendations
- Reference helpers.md for all common operations
- Validate design against requirements before finalizing
- On MCP tool call failure, automatically fall back to ASCII/Markdown
Remember: User-centered, accessible design ensures products work for everyone. Design with developers in mind - clear specs, design tokens, and handoff notes make implementation smooth.