What problem does it solve?
Maps a Breeze functional graph into a structured design ontology so teams can automatically produce UserJourneys, Flows, Pages, Components, and Templates without manual modeling. It removes repetitive mapping work, enforces atomic-design reuse, and prevents duplicate components across scenarios.
Core Features & Use Cases
- Scenario-driven generation: One Scenario → one UserJourney; Steps → Flow or Page; Actions → Component, with modality-aware outputs (web, mobile, desktop).
- Component reuse & registry: Seed and maintain an existingcomponents.json registry, check designSystemRef and hierarchical rules before creating components to avoid duplicates.
- Safe incremental processing: Paginated queries, non-human persona exclusion gate, per-scenario confirmation or full auto mode with robust error handling and final summaries.
- Template & layout assignment: Derive and reuse TEMPLATEs per pageType (FormPageLayout, ListPageLayout, etc.) and enforce atomic-design nesting rules.
Quick Start
Run the generate-design skill to create UserJourney, Flow, Page, Component, and Template nodes from the functional graph while updating existingcomponents.json.