What problem does it solve? Replacing legacy markup with an approved design system component across a repository is risky when done as a bulk refactor: ambiguous matches get silently rewritten, JS-generated markup breaks, and there is no audit trail. This Skill structures the migration into five controlled phases (discovery, mapping, pilot, batch rollout, cleanup) with explicit human confirmation at every gate. ## Core Features & Use Cases - Phased migration workflow: Discovery groups legacy marker matches into exact/similar/ambiguous buckets, Mapping builds a props/slot table from the canonical component spec, Pilot migrates only 1-2 files, and Batch Rollout applies the confirmed mapping to the rest. - Safety gates: Rollout is blocked unless the component spec and all related component specs are finalized; JS-generated markup groups require separate explicit approval; manual-review groups are never touched automatically. - Session memory and token economy: Migration state is persisted to memory logs with a scope signature so repeated runs reuse Discovery results instead of rescanning the repository. - Use Case: A team has approved a new TableRow component and needs to replace legacy .table-wrap markup across storybook and docs. Run /migrate_component TableRow to get a grouped discovery report and mapping table, approve the pilot diff, then roll out and clean up with full traceability. ## Quick Start Ask the assistant to run /migrate_component followed by your component name, for example /migrate_component TableRow, to start discovery and mapping for that component.
