design-system

To manage UI design tokens and ensure brand guideline consistency in a monorepo, this Skill analyzes repository-grounded token layers and enforces Brand→Alias→Mapped rules. It validates changes against canonical files to maintain strict alignment across your styling system.

Tracing a new brand color through design system aliases to mapped theme variables involves analyzing the repository's token layers. This Skill audits the path from the brand source through aliases to final UI styling outputs, providing evidence-backed file references and validation commands.

To audit typography and spacing tokens for UI components, this Skill analyzes repository-grounded design-system work and outputs evidence-backed analysis. It evaluates token layers, checks alignment with brand guidelines, and provides canonical file references for the targeted components.

Yes, you can implement iconography and theme variable changes across a monorepo. This Skill supports UI styling system modifications by analyzing token-layer changes, mapping the impact across layers, and ensuring updates pass design-system checks before finalizing.

Yes, enforcing design system rules requires existing token layers within the repository. This Skill relies on repository-grounded analysis to trace Brand→Alias→Mapped rules, ensuring that any token updates or UI styling changes are validated against established brand guidelines.

A repository-grounded approach for design token management ensures that styling changes are validated against actual canonical files rather than abstract configurations. This method traces layer impact, enforces brand guidelines, and outputs evidence-backed analysis to prevent UI inconsistencies.