audit-design-system

To audit design system compliance, compare your frontend project files against SPEC-CSS.md, SPEC-SPACING.md, and RULES-UI.md to identify violations. The audit enforces semantic token usage, theming consistency, and component reuse across sprints.

Design system token and theming validation ensures frontend implementations use semantic tokens consistently and support light and dark mode. This process checks your project against established SPEC files to maintain cohesive UI theming.

Enforce component reuse by auditing frontend code against RULES-UI.md to flag custom inline styling violations. The audit promotes existing component usage over custom styles and labels violations by priority for quick remediation.

Yes, running a design system audit requires alignment with SPEC-CSS.md, SPEC-SPACING.md, and RULES-UI.md. These SPEC files define the invariant checks needed to validate token usage and component reuse across the project.

Yes, you can check design handoffs for light and dark mode theming support by validating semantic token usage across the project. The audit ensures theming consistency by flagging areas where dark mode support is missing or incorrect.

The best way to flag design system violations is to run an audit that checks implementations against your SPEC files and applies priority labels to each violation. This prioritization guides remediation efforts across sprints and design handoffs.