design-system-audit

A design system audit identifies inconsistencies and debt by evaluating tokens, colors, typography, spacing, and components across cross-project repositories. It captures token inventories and design-to-code gaps, producing a structured audit report and storage-ready artifacts for implementation teams.

You document a design token inventory by scanning cross-project design repos to capture color, typography, spacing, and component variant tokens. This visual inventory identifies missing semantic tokens and naming inconsistencies, outputting a structured token model and storage-ready artifacts.

The best way to plan a design system refactor is to generate an audit report identifying design-to-code gaps and naming inconsistencies. This provides reusable templates and playbooks for token consolidation, guiding practical remediation steps to reduce design debt across projects.

Yes, a design system audit identifies missing semantic tokens by performing a consistency analysis that compares your visual inventory against the codebase. It highlights tokenization gaps and naming inconsistencies, providing structured guidance for establishing a complete semantic token structure.

Yes, the audit generates storage-ready artifacts by outputting a structured design token model and audit report. These artifacts are saved to the designated memory directory, providing implementation teams with actionable documentation for refactors and token consolidation.