apply-design-system

A design system migration audits each Figma section to determine if it can use an exact library swap or must be composed from primitives. It preserves backups and validates each staged change with screenshots to eliminate UI drift.

The best audit approach inventories each top-level section to classify it as connected, swappable, or requiring primitive composition. This multi-section reconciliation prioritizes holistic fixes over isolated changes to ensure UI consistency.

Yes, the staged workflow backs up the target frame before making any changes. It then applies section strategies like exact-swap or compose-from-primitives incrementally on controlled sections to safely reconcile the design.

Yes, component reconciliation requires access to Figma's get_metadata and get_screenshot capabilities alongside design-system search. These enable the workflow to identify mismatches, validate each staged change visually, and ensure correct library mapping.

For sections that cannot be swapped, define a strategy to compose them from design system primitives or mark them as blocked. This ensures bespoke sections are still aligned with the system's foundational elements where possible.

Avoid automated migration for sections marked as blocked where primitive composition fails or specific interaction logic cannot match the library. The staged workflow controls changes section-by-section to prevent unvalidated drift in complex areas.