design-compose

Enforce design-system consistency by running automated checks that validate design tokens and prevent undocumented components after each file write. This ensures UI builds rely on existing components rather than raw HTML, catching drift early via logs.

Validate design tokens automatically by triggering validation scripts after each write operation. The checks read configuration files like paths.json and composition-rules.json to ensure token usage complies with the design system.

Prevent undocumented components by enabling automated governance checks that flag new components and prompt catalog updates. This keeps the design system authoritative by ensuring all components are mapped in component-map.json before use.

Automated checks can stop raw HTML usage by validating imports and token application after each file write. Scripts like check-imports.py ensure components and pages rely on existing design system elements rather than custom code.

Configuration files are required to run design system validation. The automated checks read paths.json, component-map.json, and composition-rules.json to understand valid tokens, components, and rules before providing feedback via logs.

UI composition triggers drift warnings when validation scripts detect raw HTML, missing design tokens, or undocumented components. The automated checks run after each write to flag these issues and prompt catalog updates for compliance.