design-system

To audit a design system, you identify naming inconsistencies, token gaps, and hardcoded values across components. This process guides token coverage audits and generates standard documentation to prevent UI drift in large web applications.

Token coverage audit is the process of identifying token gaps and hardcoded values across components. You need it when maintaining a large web application design system to ensure a coherent UI language and prevent component drift.

You generate component documentation by enforcing frontmatter-based metadata in SKILL.md files. This standardizes component usage and variants while integrating accessibility notes directly into the design system documentation.

Yes, this approach applies specifically to large design systems in web applications. It reads available assets and supports optional scripts and references to handle extensive component libraries and identify inconsistencies.

The best way to prevent design system drift is regularly auditing components to identify naming inconsistencies and token gaps. Extending new patterns to align with existing tokens maintains a coherent UI language across releases.