1. Habit
  2. Skills
  3. Migrate Radix to Base skill
shadcn-ui · 29K installs

Migrate Radix to Base skill
Runs by itself, daily migration step.

One component migrated per run.

Install the Migrate Radix to Base skill and make it a habit: follow https://gethabit.dev/skills/shadcn-ui/migrate-radix-to-base.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

29K installs126K starsMIT licenceSource on GitHub ↗

Migrate Radix to Base

by shadcn-ui · 29K installs

The skill

The migrate radix to base skill moves shadcn wrappers and React code from Radix UI to Base UI step by step, with golden pairs, typechecks and a report per component.

Only when you ask.

The habit

One component migrated per run.

↻ Runs by itselfdaily migration step

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

daily migration step. Runs in Claude Code routine.

  • ↻ daily migration step
  • 0 9 * * 1-5

02

It checks its work

typecheck, build, no radix. If a check fails, it stops.

  • ✓typecheck passes after each consumer
  • ✓build passes against the baseline
  • ✓grep for radix-ui and @radix-ui is clean on the migrated files

03

It remembers

migration reports. The next run reads it first: remaining wrappers on Radix and in-progress -base files.

.migration/<component>.md

One run, step by step.
Then it stops.

Stop ruleStops after one component per run.

  1. 01

    Preflight

    Run npx shadcn@latest info --json, detect the package manager and require a clean tree.

  2. 02

    Baseline

    Run typecheck and build before touching dependencies.

  3. 03

    Pick the leaf

    Choose a wrapper whose own imports are already on Base UI.

  4. 04

    Golden pair

    Fetch the base variant by URL, or use the transformation engine for custom code.

  5. 05

    Write -base file

    Write <component>-base.tsx and keep the original untouched.

  6. 06

    Repoint consumers

    Move consumers one at a time with consumer-props.md and typecheck each.

  7. 07

    Finalize

    Delete the original, rename, commit, and write .migration/<component>.md.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Migrate Radix to Base skill helps.

Use it when

  • ✓ You move a shadcn project to Base UI
  • ✓ You migrate one Radix component
  • ✓ You need a report per component

Skip it when

  • – The project does not use Radix
  • – You want a one-shot rewrite with no checks

Questions

Migrate Radix to Base skill, answered.

Will it touch cmdk, vaul or sonner?

No. Those are not Radix, and the reports list them as left alone.

Does it fix behavior changes?

No. It flags them in the report for you to check by hand.

How do I install the Migrate Radix to Base skill?

Copy the prompt at the top into your agent. It installs the skill from shadcn-ui/ui and sets up the habit. Or run npx skills add shadcn-ui/ui --skill migrate-radix-to-base.

Is the Migrate Radix to Base skill free?

Yes. It is published under MIT. Habit is free too.

Migrate Radix to Base. Now as a habit.

Install the Migrate Radix to Base skill and make it a habit: follow https://gethabit.dev/skills/shadcn-ui/migrate-radix-to-base.md

  • Free
  • No account
  • Undo in one line

All shadcn-ui skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by shadcn-ui, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.