design-system-audit

Auditing design system drift involves scanning tokens, typography, spacing, and color values across your repository to identify inconsistencies. This read-only evaluation surfaces P0–P3 severity findings with file:line evidence for design and engineering handoffs.

Design system drift occurs when token values, components, or styles diverge from canonical definitions. You should check for it during quarterly audits, pre-release design reviews, and design-token governance checks to maintain alignment.

Yes, a read-only design audit evaluates tokens, color values, typography, spacing, and motion across the src/design, tokens, and components areas without modifying source files, ensuring canonical alignment remains intact during the review.

The best way to report design system inconsistencies is through evidence-first reporting with file:line citations and P0–P3 severity levels. This approach guides handoffs to design or engineering teams by prioritizing drift findings accurately.

Yes, the design audit evaluates accessibility implications alongside tokens, color values, typography, spacing, and motion. It surfaces these findings as P0–P3 severity issues with file:line evidence for comprehensive design-token governance.

The primary limitation is that the audit is strictly read-only and cannot modify code. It applies specifically to the src/design, tokens, and components areas to surface drift findings, requiring separate manual implementation for any recommended fixes.