Why It Matters
Token drift occurs when design tokens get out of sync between design tools and code. A designer updates color.primary in Figma but the CSS variable isn't updated. Or a developer adds a new spacing token that doesn't exist in design. Over time, these small drifts compound into significant inconsistencies between designed and implemented products.
Examples
1
The primary button is #0066CC in Figma but #0052A3 in the React component library.
2
Figma uses 8px/16px/24px spacing while code has 8px/12px/16px/24px/32px.
3
A new icon token was added in code for dark mode but never reflected in the Figma library.
How BiblioKit Helps
ComponentQA helps identify token drift by auditing designs for hardcoded values and flagging tokens that may need synchronization.
Related Terms
Design Tokens
Named, platform-agnostic values that store design decisions like colors, spacing, typography, and shadows, enabling consistent styling across design tools and code.
Design Handoff
The process of transferring design specifications, assets, and context from designers to developers for implementation.
Design System Audit
A systematic review of design files to assess adherence to design system standards, identify inconsistencies, and find components that have drifted from their source.
Design Ops
The practice of optimizing design team operations through processes, tools, and systems that enable designers to work more efficiently and effectively.
Explore More Design Terms
Browse our complete glossary of Figma and design systems terminology.