bmad-ux

Plan UX patterns and produce DESIGN.md and EXPERIENCE.md design specification documents.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-ux-shaahy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-ux
Source: https://github.com/shaahy/quicknav-desktop/tree/main/A%20%E6%95%99%E7%A8%8B%E9%9B%86%E5%90%88/BMAD-METHOD%E6%8A%80%E8%83%BD%E9%80%9F%E6%9F%A5/source-v6.10.0/src/bmm-skills/2-plan-workflows/bmad-ux
Command: npx skills add https://github.com/shaahy/quicknav-desktop --skill bmad-ux-shaahy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Turning vague product ideas into consistent, machine-readable UX design specifications is hard; this Skill facilitates a structured discovery process and produces two canonical contract documents that downstream architecture and development work can rely on. ## Core Features & Use Cases - Dual specification spines: Generates DESIGN.md (visual identity tokens per the Google Labs design.md spec) and EXPERIENCE.md (information architecture, states, interactions, accessibility, key flows) that cross-reference each other. - Three operating modes: Create new UX specs from scratch, Update existing spines with change tracking via a memlog, or Validate spine pairs with a multi-lens reviewer gate and consolidated HTML/Markdown validation reports. - Creative tooling: Renders HTML color themes, design directions, Excalidraw wireframes, and key-screen mockups on demand to help users decide visually. - Use Case: A product team starting a new app says "help me plan the UX"; the skill elicits requirements through discovery, renders candidate design directions, and finalizes DESIGN.md and EXPERIENCE.md ready for architecture and story development. ## Quick Start Ask the assistant to create UX design specifications for your product idea and it will guide you through discovery into finalized DESIGN.md and EXPERIENCE.md documents.

Frequently Asked Questions about bmad-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a UX design specification with an AI assistant?▼

Invoke the skill with a request like "lets create UX design" and it runs a discovery phase capturing your decisions into a memlog, then distills them into DESIGN.md and EXPERIENCE.md. You can choose a fast path with assumption tags or a coaching path with creative tools.

What is the difference between DESIGN.md and EXPERIENCE.md?▼

DESIGN.md owns how the product looks: color, typography, spacing, shape, and component tokens per the Google Labs design.md spec. EXPERIENCE.md owns how it works: information architecture, voice, state patterns, interaction primitives, accessibility, and key flows, referencing DESIGN.md tokens by name.

Can it work with existing design systems like shadcn or MUI?▼

Yes. When a UI system is named in the Foundation section, both spines inherit from it. DESIGN.md specifies only brand-layer token deltas referencing the system's defaults, and EXPERIENCE.md specifies only the behavioral delta.

How do I validate an existing UX specification?▼

Use the Validate intent on a workspace containing DESIGN.md and EXPERIENCE.md. A rubric walker checks flow, token, component, state, and visual reference coverage, optional reviewer lenses run in parallel, and results are synthesized into validation-report.html and validation-report.md.

Does it support headless or automated runs?▼

Yes. When invoked headless with a structured payload specifying intent and inputs, it completes the run without interaction and returns a JSON result with status, artifact paths, assumptions, and open questions. Creative tools are off by default in headless mode.