dux-design-md

To generate a design system markdown file, provide a visual brief with at least three hero references, one anti-reference, and a voltage moment. The system translates this into a rigorous DESIGN.md using the nine-section token schema.

A DESIGN.md token schema serves as the single source of truth for deterministic downstream generation of prototypes and screens. It enforces a one-to-one YAML-to-prose invariant to ensure consistent UI architecture.

You can update YAML design tokens through targeted update routing that preserves the YAML-to-prose one-to-one invariant. This ensures the markdown structure remains lint-ready while applying specific changes.

Yes, headless JSON or YAML briefs are supported for automated flows. The system routes these inputs to seed or create a new DESIGN.md, translating the structured data into the nine-section token schema.

The generator rejects brief inputs when they are bland or underspecified. It enforces a non-nerfable workflow that requires concrete references, anti-references, and explicit constraints before generating any tokens.

Yes, configuration loading from the project's _bmad/config.yaml dux section is required. This configuration drives the strict token validation and workspace decision logging during the authoring process.