design-system

To audit a design system for inconsistent naming and hardcoded values, run a consistency review that checks component variants, states, and token coverage. This identifies undocumented accessibility behavior and produces structured outputs with prioritized next actions.

Design token coverage is the extent to which UI components use centralized variables instead of hardcoded values. Checking token coverage prevents UI bugs and ensures visual consistency, solving the problem of design systems drifting out of sync during product delivery.

Documenting component variants, props, and states involves generating structured UI documentation that includes accessibility behavior. This ensures teams implement components correctly by providing clear, reusable docs that align with existing design system principles.

Yes, a design system audit verifies component completeness by checking for missing states and variants across your UI. It produces a structured output covering naming consistency and token gaps, then proposes prioritized next actions to fix incomplete documentation.

The best way to design a new component pattern is to apply pattern extension, which matches existing principles and reuses current design tokens. This defines the API, variants, states, and accessibility guidance for the new pattern.

You should run a consistency audit when your design system drifts out of sync, causing UI bugs and slower product delivery. This process identifies undocumented tokens, verifies variants and props, and produces prioritized next actions to restore system consistency.