bmad-ux

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-ux-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-ux
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-ux
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-ux-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Turning a product vision into consistent, developer-ready UX specifications is slow and error-prone; this Skill facilitates structured UX discovery and distills decisions into two canonical contract documents. ## Core Features & Use Cases - Dual specification spines: Produces DESIGN.md (visual identity tokens per the Google Labs spec) and EXPERIENCE.md (information architecture, states, interactions, accessibility, key flows) that cross-reference each other. - Three operating modes: Create new UX specs from discovery, Update existing spines with conflict detection, and Validate spine pairs with a multi-lens reviewer gate. - Creative tooling: Renders HTML color themes, design directions, Excalidraw wireframes, and key-screen mockups to help users decide visually. - Use Case: A product team starting a new app says "let's create UX design"; the Skill elicits their vision 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 and answer its discovery questions about brand, platforms, and 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 UX design specifications with this Skill?▼

Say "let's create UX design" or "create UX specifications" to trigger Create mode. The Skill runs a discovery phase capturing your decisions in a decision log, then distills them into DESIGN.md and EXPERIENCE.md at finalize.

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 spec. EXPERIENCE.md owns how it works: information architecture, state patterns, interaction primitives, accessibility, and key user flows.

Does it support 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, and EXPERIENCE.md specifies only the behavioral delta over the system's defaults.

Can it validate an existing UX specification?▼

Yes, Validate mode critiques an existing DESIGN.md and EXPERIENCE.md pair without changing it. It runs a rubric walker covering flow, token, component, and state coverage, plus optional reviewer lenses, and writes an HTML and Markdown validation report.

What creative tools are included for visual exploration?▼

Default renderers produce HTML color theme variations, HTML design direction mockups, Excalidraw IA and flow wireframes, and 1:1 key-screen HTML mockups. Artifacts are written to a .working folder and promoted to mockups or wireframes at finalize.

When should I not use this Skill?▼

Route elsewhere when the request is a PRD, system architecture, game UX, or agent building; the Skill itself redirects those to the appropriate BMad skills. It is a UX specification facilitator, not a code generator.