What problem does it solve? Moving components from a legacy frontend into a shared design system monorepo is error-prone: hardcoded styles slip through, barrel exports get forgotten, variants are not declared in the theme, and stories are skipped. This Skill standardizes the entire migration so every ported component follows the same theme, typing, and documentation rules. ## Core Features & Use Cases - Structured migration workflow: Analyzes the legacy component's props, MUI usage, variants, and business-logic dependencies before designing the DS version. - Theme and token enforcement: Maps legacy variants to MUI theme variants with module augmentation, replacing hardcoded colors and spacing with design tokens. - Deterministic verification: Validates barrel exports via grep/node checks, runs pnpm build:react, and executes Storybook test-runner regression checks. - Use Case: A designer asks to move the legacy Button into the design system. The Skill creates packages/react/src/components/Button/ with typed props, updates the barrel export, adds a Storybook story covering all variants, and writes a migration spec to .agents/components/Button-migration.md. ## Quick Start Ask the agent to migrate the Button component from the legacy frontend into the design system monorepo with its story and theme variants.