bmild-ux

Generate structured ux-design.md documents covering UX decisions and edge states.

3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/micfre/BMILD --skill bmild-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmild-ux
Source: https://github.com/micfre/BMILD/tree/main/.agents/skills/bmild-ux
Command: npx skills add https://github.com/micfre/BMILD --skill bmild-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

BMILD projects often suffer from vague, incomplete UX requirements that lead to rework, missed edge states, and misalignment between design and implementation teams. This skill eliminates that friction by guiding structured elicitation of interaction models, user flows, visual design language, and testable UX decisions.

Core Features & Use Cases

  • Structured UX Artifact Generation: Produces compliant ux-design.md documents covering all required sections per BMILD's completion criteria, including information architecture, user flows, interaction models, edge states, and accessibility.
  • Workflow Mode Adaptation: Automatically selects the correct workflow (new UX design, refinement of existing designs, or resolution of UX-owned handoff items) based on project artifact state.
  • Cross-Team Governance Integration: Routes cross-artifact conflicts to the appropriate BMILD persona, distills global design patterns into the project DESIGN.md when applicable, and maintains semantic memory via context.md and context-map.md.
  • Use Case: When building a new user dashboard feature for your BMILD project, use this skill to capture all UX requirements, edge cases, and design rationale so implementation and verification teams have a clear, testable contract.

Quick Start

Use the bmild-ux skill to create a structured UX design document for the new user onboarding initiative in your BMILD project.

Frequently Asked Questions about bmild-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure UX design documentation for spec-driven development?

To create testable UX design contracts, you need to document interaction models, information architecture, user flows, edge states, and accessibility requirements. This structured elicitation ensures downstream implementation teams have clear, observable design contracts that prevent rework and misalignment.

What is included in a spec-driven UX design document?

A spec-driven UX design document includes information architecture, user flows, interaction models, edge states, and accessibility requirements. It serves as an observable contract that aligns with product and architecture constraints to support downstream implementation and verification.

How do I resolve cross-artifact conflicts in UX design workflows?

Resolving cross-artifact conflicts in UX design workflows requires routing discrepancies to the appropriate cross-team persona. Global design patterns are then distilled into the project design documentation while maintaining semantic memory via context and context-map files.

Can I use structured UX design for refining existing user flows?

Yes, structured UX design supports refining existing user flows by automatically adapting the workflow mode based on project artifact state. It handles new UX design generation, refinement of existing designs, and resolution of UX-owned handoff items.

Why does unstructured UX design documentation cause rework in development?

Unstructured UX design documentation causes rework because it leads to vague requirements, missed edge states, and misalignment between design and implementation teams. Structured elicitation of testable UX decisions eliminates this friction by establishing clear design contracts.