Skip to content

Conversation

@azuma520
Copy link

Summary

This PR extends Issue #1137 (KB integration into create-ux-design) by adding a complete Design System Generator Workflow that consumes the UX Specification output.

Relationship to #1137

Epic Scope Status
Epic 1 KB Integration into create-ux-design (Step 8, 12) ✅ Complete
Epic 2 Design System Generator Workflow ✅ Complete (this PR)

The two workflows work together:
create-ux-design (Epic 1) → UX Spec → generate-design-system (Epic 2) → Design System Files

What's New in This PR

Generate Design System Workflow

  • src/modules/bmm/workflows/4-implementation/generate-design-system/
  • Automatically generates 4 design system files from UX Spec
  • KB integration for missing token suggestions
  • Validation mechanism for output quality

Output Files Generated

  • design-tokens.json - Token definitions with source tracking
  • theme.css - CSS custom properties with dark mode support
  • globals.css - Base styles, reset, components
  • component-specs.json - Component specifications for dev handoff

Test Samples & Report

  • test-samples/integration-test-report.md - Full validation report
  • test-samples/sample-a/ - Complete test data (AquaFlow SaaS project)

Test Results

Metric Target Result
KB Reference Rate (KB-hit) > 70% ✅ 100%
Completeness Rate 100% ✅ 100%
Format Correctness 100% ✅ 100%
Dev Usability All pass ✅ PASS

Refs #1137

…ndations

- Add KB search integration to step-08 (color, typography domains)

- Add KB search integration to step-12 (ux domain with severity sorting)

- Add Component Resources section to ux-design-template

- Include fallback handling for graceful degradation

Closes bmad-code-org#1137
- Validate componentLibrary, effectsLibrary, referenceSites from UX spec

- Display UX component guidance during story development

- Warn if UX spec exists but missing Component Resources
Building on Issue bmad-code-org#1137 (KB integration into create-ux-design):
- Epic 1: UX Workflow KB Integration (Step 8, 12)
- Epic 2: Design System Generator Workflow (NEW)
  - Auto-generate design-tokens.json, theme.css, globals.css, component-specs.json
  - KB suggestion for missing tokens
  - Validation mechanism for output quality

Includes integration test report and sample-a test data.

Refs bmad-code-org#1137
@azuma520
Copy link
Author

Hey! 👋

I noticed that the BMM workflow was missing a proper process and KB support for generating design tokens, CSS variables, and component specs. The Dev Agent can still do it, of course, but without a structured workflow and KB suggestions, the output quality might be inconsistent, which could affect downstream development.

So I built this Design System Generator workflow with KB integration to make the Dev Agent's output more consistent and reliable. Honestly, it wasn't easy for me, but with the help of the BMM agent crew 🙌, I managed to get it done.

Hope this helps the project!

Btw, there are some merge conflicts — feel free to resolve them however you see fit.

Merry Christmas to the maintainer team! 🎄✨

@azuma520
Copy link
Author

Update: Added strategy-based outputs for the Design System Generator (Tailwind/SCSS/Generic) and updated the validation flow accordingly. Also included the UI/UX Pro Max KB resources and
installer support to copy resources into _bmad/resources.

@azuma520 azuma520 closed this Dec 26, 2025
@azuma520 azuma520 reopened this Dec 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant