review-and-fix-design-system

To audit Figma design-system drift, initiate a read-only review of a specific Figma screen or component URL to identify concrete inconsistencies and document evidence for prioritization.

Design-system drift occurs when Figma screens or components deviate from established library or token standards, obscuring consistency and slowing delivery. You identify it by running a focused audit to find concrete inconsistencies.

No, you must choose exactly one high-signal finding for a single narrow repair. The workflow enforces guardrails to keep fixes validated and tied to library-backed targets, preventing scope creep during broader rewrites.

The best way to repair design-system drift is applying a focused, single-finding fix workflow that validates the chosen repair against library-backed or token-bound targets before applying the write.

Yes, a Figma URL is a common starting point to trigger the audit-design-system workflow, which then identifies the highest-signal drift issue on that specific screen or component for prioritization.

Documenting evidence during a design-system drift audit ensures that identified findings are prioritized effectively and that subsequent repairs remain narrowly scoped, actionable, and validated before application.