UX Blueprint Skill

When to Invoke

• Says "What should the UI look like?", "Design the UX"
• Asks "How should users interact?", "User flow?"
• Mentions "wireframes", "user experience", "interface design"
• Has PRD with UI-heavy features (Level 2-4)
• Uses words like: UX, UI, design, wireframe, interface, usability

• "What should the UI look like?"
• "Design the UX for [feature]"
• "Create wireframes"
• "User experience for [feature]"
• "Interface design"
• "User flow for [scenario]"

• No UI/interface in project (backend-only)
• PRD not ready (use bmad-product-planning first)
• Already have UX specs (skip to architecture or stories)

Mission

Inputs Required

• prd_sections: user journeys, functional requirements, constraints
• architecture_notes: technical or platform limits impacting UX
• brand_guidelines: accessibility, tone, device targets, or visual standards

Outputs

• User flows (from

  assets/user-flows-template.md.template

  )
• Wireframes (from

  assets/wireframes-template.md.template

  )
• Design system (from

  assets/design-system-template.md.template

  )
• UX requirements checklist linked to PRD and stories
• Validation plan (usability or experimentation) for quality-assurance alignment

.claude/skills/bmad-ux-design/assets/*.template

Process

1. Confirm prerequisites via

   CHECKLIST.md

   .
2. Clarify personas, scenarios, and surfaces requiring design.
3. Produce information architecture, flows, and state diagrams.
4. Document component specifications and content rules tied to requirements.
5. Define validation approach (tests, instrumentation, success signals) and share with delivery-planning and quality-assurance skills.

assets/

scripts/README.md

Quality Gates

CHECKLIST.md

Error Handling

• If requirements conflict or are missing, request clarification before designing.
• Flag technical limitations that impact user experience and loop architecture-design.
• Provide alternate recommendations when constraints prevent ideal UX outcomes.