dragoon0x/everything-design-taste

design-system-migration

Migrating between design systems, component replacement strategies, and gradual adoption.

First seen Jul 18, 2026

Installation

$ npx skills add dragoon0x/everything-design-taste --skill design-system-migration

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dragoon0x/everything-design-taste · top by installs.

npx skills add dragoon0x/everything-design-taste

Browse all from dragoon0x/everything-design-taste

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 11
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,282 B
  • docs SUMMARY.md 120 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Design System Migration

Migration Strategy

Strangler Fig Pattern

  1. New components built in new system.
  2. Old components wrapped with new system API.
  3. Gradually replace wrappers with native new components.
  4. Old system removed when no references remain.

Page-by-Page

  1. Identify the least complex page.
  2. Migrate all components on that page to new system.
  3. Move to next page in complexity order.
  4. Each page is fully migrated before moving on.

Migration Checklist

  • Inventory all existing components and their usage count.
  • Map old components to new components.
  • Identify gaps (components in old system with no new equivalent).
  • Build missing components before starting migration.
  • Create a migration guide for each component.
  • Visual regression tests for migrated pages.
  • Deprecation warnings on old components.

Timing

  • Never migrate during a feature sprint.
  • Dedicate sprints specifically for migration.
  • Celebrate milestones (10% migrated, 50%, 90%).
  • Track migration progress publicly.