theme-audit

To audit design system token coverage, scan all components against your defined themes to detect missing tokens, identify tier leakage, and validate visual consistency. This ensures every element has a corresponding value across light, dark, and brand variants.

Component tier leakage occurs when component tokens fail to correctly inherit from semantic tokens across different themes. Auditing this propagation verifies that tokens map correctly, preventing visual inconsistencies when switching between light, dark, or brand modes.

To check design system regression risks, scan your codebase for hardcoded values and incorrect CSS usage that may break during theme switches. This assessment identifies patterns that fail to resolve properly through DTCG configurations.

Yes, the design system audit validates DTCG resolver configurations to ensure tokens resolve correctly. It assesses resolver setups alongside hardcoded values to identify patterns that may cause visual glitches during light, dark, or brand theme switches.

You need to run a theme consistency audit after launching a new mode like dark mode, updating semantic tokens, or adding brand variants. It automatically scans tokens and components to catch missing values and prevent unexpected visual bugs.