BMad UX — capture the UX vision in DESIGN.md and EXPERIENCE.md
Facilitate UX vision capture into two peer contracts — DESIGN.md (how it looks, per Google Labs spec) and EXPERIENCE.md (information architecture, behavior, states, journeys)
- What
- Facilitate UX vision capture into two peer contracts — DESIGN.md (how it looks, per Google Labs spec) and EXPERIENCE.md (information architecture, behavior, states, journeys)
- Cost
- Free
- Needs
- ideally a BMad-configured project (a _bmad workspace and an active initiative; the skill falls back gracefully) — the skill is guidance the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): the BMad UX skill from @bmad-code-org — a master UX facilitator that elicits and captures the user's vision instead of imposing one. It produces two peer contracts: DESIGN.md (visual identity per the Google Labs spec — YAML frontmatter tokens for colors, typography, rounded, spacing, components, then a canonical markdown body: Brand & Style, Colors, Typography, Layout & Spacing, Elevation & Depth, Shapes, Components, Do's and Don'ts) and EXPERIENCE.md (information architecture, voice and tone, component patterns, state patterns, interaction primitives, accessibility floor, key flows with named-protagonist journeys). The workflow runs Discovery → Finalize: scan prior in-progress runs, brain dump intake, fast path (draft both spines with [ASSUMPTION] tags) or coaching path, an optional reviewer gate with selectable lenses, key-screen mock rendering, layout extraction, and handoff with both files marked final. Honest caveats: built for a BMad-configured project — activation runs `uv` scripts against a `_bmad` workspace and expects an active initiative (it offers to run the `bmad` setup skill if missing, and falls back to reading config directly); license not stated by the source repo — short listing with a link only, nothing copied. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: ideally a BMad-configured project (a _bmad workspace and an active initiative; the skill falls back gracefully) — the skill is guidance the agent follows, not software Install "BMad UX — capture the UX vision in DESIGN.md and EXPERIENCE.md" for me. It gives my agent the BMad UX facilitation workflow: elicit the user's UX vision and capture it in two peer contracts — DESIGN.md (visual identity per the Google Labs spec: YAML frontmatter tokens + canonical markdown body) and EXPERIENCE.md (information architecture, voice and tone, component/state patterns, interaction primitives, accessibility, key flows with named-protagonist journeys) — through Discovery → Finalize (intake, fast or coaching path, optional reviewer gate, key-screen mocks, handoff). IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://github.com/bmad-code-org/bmad-method/blob/main/skills/bmad-ux/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "bmad-ux". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. tell the agent what product or feature to design for; run the bmad setup skill first if there is no _bmad workspace). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.