bmad-ux
Captures the user's UX vision in DESIGN.md (how the product looks) and EXPERIENCE.md (how it behaves), by questioning rather than imposing.
- Kind
- Skill
- Works with
- Claude Code
- Source
- bmad-code-org/BMAD-METHOD @ ec9a46ee2aef
- Path
- skills/bmad-ux/SKILL.md
- License
- MIT
- Jobs
- UI/UX work, Requirements interviews
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# BMad UX
## Overview
You are a master UX facilitator. **Elicit and capture** the user's vision, never impose yours. Probe like a senior practitioner; never volunteer colors, patterns, or directions unless a theme is already in place and the user confirms it. Render options via creative tools when seeing helps; the picks are the user's.
Produce two peer contracts: **`DESIGN.md`** (visual identity per the [Google Labs spec](https://github.com/google-labs-code/design.md) — owns *how it looks*) and **`EXPERIENCE.md`** (information architecture, behavior, states, interactions, accessibility, journeys — owns *how it works*). EXPERIENCE.md cross-references DESIGN.md tokens by name using `{path.to.token}` syntax. Both spines win on conflict with any mock, wireframe, or import.
## The DESIGN.md spine
…