bmad-ux

Elicit UX requirements and produce DESIGN.md and EXPERIENCE.md specification documents.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-ux-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-ux
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-ux
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-ux-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Turning a vague product vision into concrete, developer-ready UX specifications is hard: visual identity and behavioral rules get mixed together, decisions get lost, and downstream teams receive inconsistent guidance. This Skill facilitates a structured elicitation process that captures the user's UX vision into two authoritative contract documents. ## Core Features & Use Cases - Dual specification output: Produces DESIGN.md (visual identity tokens per the Google Labs design.md spec: colors, typography, rounded, spacing, components) and EXPERIENCE.md (information architecture, state patterns, interaction primitives, accessibility floor, key flows). - Three operating modes: Create (full discovery-to-finalize workflow), Update (apply changes against prior decisions logged in a memlog), and Validate (multi-lens reviewer gate with rubric-based coverage checks and consolidated HTML/Markdown reports). - Creative tooling: On-demand renderers for HTML color themes, design directions, Excalidraw wireframes, and key-screen mockups, plus headless mode with JSON output schemas for automation. - Use Case: A product manager starting a new app says "let's create UX design" — the Skill interviews them about brand, platforms, and user journeys, then distills everything into DESIGN.md and EXPERIENCE.md files that architecture and story-planning skills can consume directly. ## Quick Start Ask the assistant to create a UX design for your product and answer its discovery questions about brand, platforms, and key user journeys.

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 this skill?

Invoke the skill with a phrase like "let's create UX design" and it enters Create mode: it binds a workspace, runs a discovery interview about brand, platforms, and user journeys, then distills decisions into DESIGN.md and EXPERIENCE.md files.

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

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

Does the skill support design systems like shadcn or MUI?

Yes. When a UI system is named in the Foundation section, both documents inherit from it: DESIGN.md tokens reference or extend the system's defaults, and EXPERIENCE.md specifies only the behavioral delta rather than restating inherited specs.

Can I validate an existing UX specification without changing it?

Yes, Validate mode critiques an existing DESIGN.md and EXPERIENCE.md pair using a rubric walker covering flow, token, component, and state coverage, plus optional reviewer lenses. It writes a consolidated validation report in HTML and Markdown without modifying the spines.

Does bmad-ux work in headless or automated pipelines?

Yes. Headless mode accepts a structured payload with intent (create, update, or validate) and inputs, skips interactive prompts, and ends with a JSON result following the schemas in assets/headless-schemas.md, including status, artifact paths, and open questions.