retrofit-planner

Run a phased retrofit: audit the system first, refine Figma variables in place preserving IDs, rebind components, sync tokens to code, capture a visual baseline, then retrofit code with dual output so old and new tokens coexist. Confirm each phase before advancing.

Rename variables in place rather than deleting and recreating them, which preserves their IDs and existing bindings. Run a binding-survival audit before and after each rename to verify binding counts are equal.

Yes. The current phase is written to a manifest on entry, so a later session reads that state and resumes at the exact phase where work stopped. The environment setup step routes back to the right phase automatically.

Capture the Chromatic baseline before any code retrofit begins, not after. Baselining after code changes throws away the signal needed to distinguish intended drift-fixes from actual regressions.

Remove old outputs only after a repo-wide token-removal guard returns zero references. Deleted Tailwind utilities are silent no-ops that type-checking and builds will not catch, so the grep-based guard is mandatory.

Use individual skills for a single isolated step, such as just the audit or just the crosswalk. Use the orchestrator for a complete end-to-end retrofit, especially one spanning multiple sessions.