feat(bmm): Extend #1137 KB Integration with Design System Generator Workflow#1190
feat(bmm): Extend #1137 KB Integration with Design System Generator Workflow#1190azuma520 wants to merge 5 commits intobmad-code-org:mainfrom
Conversation
…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
|
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! 🎄✨ |
|
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 |
|
@azuma520 thank you for this and appologies for not responding sooner, in the mix of the Holidays I missed this. I like the idea there is a real gap and would like to get something like this potentially merged in. As this one stands I will close it but would love to see something along these lines as I can see there is a gap for some of the items here, like a dedicated token generator. A few issues with this is I do not want to have to maintain going forward all the standards for the various ui platforms, and a lot of it is pretty engrained in the llms, and some less so. You did to a great job on this, and i love the data driven approach. This would make for a great optional module for someone to choose and install, potentially even multiple smaller modules based on the users chosen ui framework instead of a one size fits all, or a module with small skills targeting each framework - there are multiple options. |
2 participants
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
create-ux-design(Step 8, 12)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/Output Files Generated
design-tokens.json- Token definitions with source trackingtheme.css- CSS custom properties with dark mode supportglobals.css- Base styles, reset, componentscomponent-specs.json- Component specifications for dev handoffTest Samples & Report
test-samples/integration-test-report.md- Full validation reporttest-samples/sample-a/- Complete test data (AquaFlow SaaS project)Test Results
Refs #1137