audit-design-system

To check Figma designs for design system drift, you need to audit nodes for missing shared components, local overrides, and unbound tokens. This process identifies custom-built primitives and duplicated patterns replacing approved system variables.

Design system drift in UI components occurs when designers use custom-built primitives, local overrides, and unbound tokens instead of approved shared components. This structural inconsistency introduces duplicated patterns and raw visual values that bypass established system variables.

To audit Figma components before handoff, review the screen for structural evidence of inconsistent component usage and tokenization gaps. Identify missing shared components and local overrides that should be replaced with approved system components.

Yes, you can detect unbound design tokens in Figma files by evaluating instances and variables for raw visual values. The audit identifies where repeated sibling structures and custom primitives bypass approved system variables.

Yes, this design audit works for repeated sibling structures in Figma by identifying duplicated patterns that indicate design drift. It evaluates these structures against shared components to recommend potential system replacements.