bmad-ux

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

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-ux-unbakedcosmos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-ux
Source: https://github.com/unbakedcosmos/thumbnailer/tree/main/.claude/skills/bmad-ux
Command: npx skills add https://github.com/unbakedcosmos/thumbnailer --skill bmad-ux-unbakedcosmos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Turning vague product ideas into consistent, buildable UX specifications is hard: visual identity and behavioral rules end up scattered across chats, mocks, and memory. This Skill facilitates a structured elicitation process and distills the results into two canonical contract documents. ## Core Features & Use Cases - Dual specification spines: Produces 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 modes: Create (facilitated discovery with creative tools like HTML color themes, design directions, and Excalidraw wireframes), Update (revise existing spines with conflict surfacing), and Validate (multi-lens reviewer gate with a consolidated HTML/Markdown report). - Decision audit trail: Every decision is logged to a memlog, working artifacts are promoted to mockups/ or wireframes/ at finalize, and headless mode supports automation with JSON output schemas. - Use Case: A product team starting a new app runs the skill to walk through brand, IA, and key flows, ending with finalized DESIGN.md and EXPERIENCE.md files that architecture and story-development steps consume directly. ## Quick Start Ask the assistant to create UX design specifications 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 request like "create UX specifications" and it runs Discovery: brain-dump intake, source scanning, creative tools for visual decisions, and named-protagonist journeys. At Finalize it distills everything 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, shape tokens, and component visuals per the Google Labs design.md spec. EXPERIENCE.md owns how it works: information architecture, state patterns, interaction primitives, accessibility behavior, and key flows.

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

Can I validate an existing UX specification instead of creating one?▼

Yes. The Validate intent runs an opt-in reviewer gate with selectable lenses, including a rubric walker covering flow, token, component, and state coverage. Findings are synthesized into validation-report.html and a Markdown twin.

Can the skill run headless in an automated pipeline?▼

Yes. Headless mode activates when invoked by another skill or automation with pre-supplied inputs. It skips greetings and creative tools by default, completes the detected intent, and ends with a JSON payload matching the schemas in assets/headless-schemas.md.