design-token-critic

You can audit design tokens by validating token tiers, naming conventions, and aliasing strategies against design memory to identify structural debt and verify parity across CSS, Tailwind, and Figma variables.

Design token drift is caused by organic growth leading to inconsistent naming and missing values. You check for it by performing an evidence-backed audit to find raw values being used instead of established tokens.

Yes, you can verify parity between CSS, Tailwind, and Figma variables. The process checks color contrast against WCAG standards and evaluates typography scales to ensure cross-platform compliance.

Yes, you need access to token source files and design memory artifacts. These inputs are required to perform structural verification and compliance checks against your established design system documentation.

You validate color contrast ratios by checking your token source files against WCAG standards. This compliance verification identifies tokens that fail accessibility requirements during the architectural audit.