design-system-governance

Design token drift detection compares token values across Figma design systems and code implementations (CSS variables, Tailwind config, design tokens JSON) to surface inconsistencies. Extract tokens from Figma via MCP, parse code token sources, normalize names, and compare sets to identify mismatches requiring remediation.

Run governance checks periodically before releases, after Figma updates, during design system migrations, when onboarding new projects, pre-implementation, and post-implementation. These audits verify token consistency across your design system and code baseline.

Yes. Governance checks generate drift reports and automatically create Wrangler issues categorized by drift type with recommendations for reconciliation, eliminating manual tracking and enabling systematic token remediation across your codebase.

The Skill parses design tokens from CSS variables, Tailwind configuration files, and design tokens JSON formats, normalizing token names across sources to enable accurate drift comparison and detection of inconsistencies.

No. The Skill detects drift, classifies severity, generates reports, and creates issues with reconciliation recommendations, but requires manual resolution. This governance-first approach ensures intentional token alignment decisions.