What problem does it solve? Design tokens in code and Figma variables drift apart over time, causing inconsistent colors, spacing, and typography between design and implementation. This Skill detects that drift, reports it in detail, and applies corrections only after explicit human approval. ## Core Features & Use Cases - Drift Detection and Reporting: Normalizes tokens from both sides into canonical rows and classifies every difference (missing tokens, value mismatches, alias mismatches, mode mismatches, broken aliases) with before/after values. - Approval-Gated Writes: Always produces a dry-run summary first and stops for explicit confirmation before any write call to Figma, with archive-only deletion as the default policy. - Configurable Sync Policies: Supports direction (code_to_figma, figma_to_code, bidirectional), conflict policies (prefer_code, prefer_figma, manual_review), naming normalization, and mode mapping. - Use Case: A design system team updates color tokens in tokens.json and needs Figma variables to match. The Skill diffs both sources, lists each drift item, waits for a "yes" confirmation, then applies creates, updates, and alias fixes in a safe order and verifies zero remaining drift. ## Quick Start Ask the assistant to compare the tokens.json file in the repository with the Figma variables and show a dry-run drift report before applying any changes.
