Design System Hub
Use this hub when
- teams are forking components
- accessibility defects repeat across products
- tokens do not support multiple brands or modes
- component APIs are becoming unstable
- GenUI needs a safe component registry
Reading path
| Step | Read |
|---|---|
| Foundation | part-vii/design-systems-ui-architecture, part-vii/token-architecture-semantic-systems |
| Component APIs | part-vii/durable-component-api-design, part-vii/headless-primitives-composition |
| Accessibility | part-vii/accessibility-contracts-component-layer, part-vii/inclusive-component-recipes |
| Governance | part-vii/system-evolution-governance, part-iv/design-system-package-architecture |
| Examples | part-xii/completed-examples/completed-design-system-api-review, part-xii/completed-examples/completed-genui-registry-contract |
| Capstone | capstones/capstone-enterprise-design-system-platform, capstones/solution-packs/capstone-solution-pack-enterprise-design-system |
Artifacts to produce
- token taxonomy ADR
- component API review
- accessibility contract
- package graph
- adoption scorecard
- migration plan
Review prompts
- What behavior belongs in primitives, styled components, recipes, or product wrappers?
- How does the API prevent accessibility regressions?
- What migration support exists before deprecation?
- What scorecard shows healthy adoption?
Source lens
Use Part VII chapters, the completed design-system API review, and the enterprise design-system capstone as the main source chain.