Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-ux
Solutioning-phase UX planning skill (optional; activate when the project has a UI). Produces TWO planning documents: DESIGN.md (the visual system — design tokens, color palette, typography, spacing, component specs, WCAG 2.1 AA contract) and EXPERIENCE.md (user journeys, flow diagrams, screen states, error/empty/loading handling).
Passed 15 of 20 test cases with the skill, and 9 of 20 without it.
and 7 more in the full report
7 fixed10 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
Produces the two-document UX contract that downstream story authors and the external dev tool rely on. This is a planning skill. It produces specifications, not code.
Under bmad-output/ (or the folder in config.yaml):
bmad-output/
├── DESIGN.md # Visual system: tokens, components, accessibility contract
└── EXPERIENCE.md # Journeys, flows, states, error/empty/loading specs
Both documents are locked planning artifacts. The external dev tool may read them
but must not edit them. All design decisions should be recorded in decision-log.md.
decision-log.md explaining what changed and why.Before drafting, read (in order):
bmad-output/config.yaml — project name, track, output folder.bmad-output/project-context.md — user personas, platform targets, constraints.bmad-output/prd.md (if present) — feature list, user stories, acceptance criteria.bmad-output/architecture.md (if present) — component boundaries, API contracts.If any of these are missing, ask the user for the key inputs before proceeding.
Use ${CLAUDE_PLUGIN_ROOT}/skills/bmad-ux/templates/design.template.md.
test cases passed, vs 9 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.