Design System Migration logo

Design System Migration

Community
Dragoon0x
design-system-migration

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

Overview

PublisherDragoon0x
Repositoryeverything-design-taste
Skill namedesign-system-migration
Stars
13
Forks
2
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Dragoon0x on GitHub. Read the source before you install it.

Installation

Install the Design System Migration AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Dragoon0x/everything-design-taste/tree/main/skills/design-system-migration
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Dragoon0x/everything-design-taste.git /tmp/everything-design-taste
mkdir -p .claude/skills
cp -r /tmp/everything-design-taste/skills/design-system-migration .claude/skills/design-system-migration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Design System Migration in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Design System Migration on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Design System Migration is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Design System Migration AI skill do?

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

Why use Design System Migration on TypingMind?

Because you install it once and use it with any model. Design System Migration is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Design System Migration in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dragoon0x/everything-design-taste/tree/main/skills/design-system-migration. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Design System Migration?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Design System Migration?

As many as you like. As long as a model supports skills, you can use Design System Migration with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Design System Migration AI skill free?

Yes. It is published on GitHub by Dragoon0x under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇