audit-design-system

To audit a Figma screen for design system drift, provide a Figma node URL or fileKey/nodeId to identify token misbindings, local overrides, and missing shared primitives. The audit examines structural evidence and presents actionable replacement suggestions.

Design system drift in Figma components occurs when designs diverge from established tokens and primitives through local overrides, token misbindings, or unbound tokens. This hindrance affects consistency and theming across an application.

Yes, you can flag missing shared primitives in a Figma board by auditing individual screens, components, or boards. The audit locates instances of unbound tokens and duplicated patterns to surface missing primitives.

To identify token misbindings in Figma, audit the target screen or component to examine structural evidence like instances versus frames. The audit flags token misbindings and local overrides, providing actionable replacement suggestions.

The best way to review a Figma component library for migration is to audit screens to surface drift and drive a scope-defined remediation pass. This identifies divergences from the design system and flags missing shared primitives.

Yes, the audit provides replacement suggestions for local overrides. It examines structural evidence in Figma to present guided remediation cues, suggesting candidate replacements from the audited library and routing to downstream skills.