architecture-review

Design token architecture audits evaluate your Primitive→Semantic→Component hierarchy for structural health, naming consistency, and proper separation of concerns. This identifies technical debt, missing state tokens, and scaling bottlenecks before they fragment your system.

Enforce consistency by reviewing naming conventions, variant patterns, size systems, and state management across all tokens and components. Tailwind @theme integration and Props API standardization ensure developers use the system correctly and reduce prop-naming collisions.

An architectural review identifies inconsistencies in prop naming, missing state tokens, direct primitive usage in components, and gaps in documentation or pattern uniformity. These findings explain adoption friction and guide refactoring priorities.

A design token architecture review generates a concrete refactoring plan that maps current violations to target state, prioritizes changes by impact, and flags cross-component dependencies. This enables staged migration with minimal breakage.

Verify Primitive tokens are abstract, Semantic tokens map to intent, Component tokens cover all interactive states (base, hover, focus, disabled), naming follows a consistent convention, and variant patterns scale predictably across the system.

The architecture-review Skill requires pnpm as a package manager. If your project uses npm or yarn, you'll need to adapt the setup, but the core audit logic applies to any Tailwind-based design system.