migrate-radix-to-base: move React components from Radix UI to Base UI
Migrate shadcn wrappers or hand-rolled Radix code to @base-ui/react — one component or whole projects
- What
- Migrate shadcn wrappers or hand-rolled Radix code to @base-ui/react — one component or whole projects
- Cost
- Free
- Needs
- a React project using Radix UI (shadcn wrappers or hand-rolled compositions); Node.js; git with a clean tree; @base-ui/react installed alongside radix (radix removed only after the last component migrates)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official shadcn repo's migration workflow for moving React components from Radix UI to Base UI: a preflight ritual (detect package manager, require a clean git tree, baseline the build), then the strategy — golden-pair first via the shadcn CLI (`shadcn add <component> --overwrite` for whole-project mode, fetched base variants written to `<component>-base.tsx` in progressive mode, three-way `git merge-file` to replay customizations onto base variants), or the transformation engine for hand-rolled Radix code (imports, `asChild`→render, Portal→Positioner→Popup, per-family props tables, class-mapping renames). Progressive (strangler-fig) mode is the default: repoint consumers one at a time, flip `components.json` only after the last wrapper. Hard rules are spelled out: never touch non-Radix libs (cmdk, vaul, sonner, input-otp, react-day-picker, recharts), components without a Base UI counterpart get honest replacements (AspectRatio → CSS div, Label → native `<label>`), behavior deltas are flagged never silently patched, and every component gets a report in `.migration/<component>.md`. By @shadcn-ui, listed here with credit to its creator. Honest caveats: official shadcn skill, tracking the registry's current Base UI variants — legacy styles (new-york etc.) have no Base counterpart and are classification-only; requires a clean git tree and a working baseline build before touching anything. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
migrate-radix-to-base is a free Muse skill and the official shadcn migration workflow for moving components from Radix UI to Base UI, one component or whole projects. It starts with a preflight ritual of detecting the package manager and baselining the build, then uses golden-pair migration via the shadcn CLI or a transformation engine for hand-rolled Radix code.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox and failed · Nov 18, 2026 · Needs pnpm, npm cannot install it📌 Pinned version: commit c2a6784Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a React project using Radix UI (shadcn wrappers or hand-rolled compositions); Node.js; git with a clean tree; @base-ui/react installed alongside radix (radix removed only after the last component migrates) Install "migrate-radix-to-base: move React components from Radix UI to Base UI" for me. Give my agent the Radix-to-Base-UI migration workflow — preflight, golden-pair strategy via the shadcn CLI, the transformation engine for hand-rolled code, progressive and whole-project modes, hard rules and per-component reporting Repository: https://raw.githubusercontent.com/shadcn-ui/ui/c2a67849be260701852b0977ba15eb5f3a0ce2a4/skills/migrate-radix-to-base/SKILL.md Pinned version: install the code at commit c2a67849be260701852b0977ba15eb5f3a0ce2a4 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and its reference files) for the shadcn-ui-ui-migrate-radix-to-base skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "shadcn-ui-ui-migrate-radix-to-base". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. start from a clean git tree with a passing build baseline, then ask to migrate a single component first). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- c2a6784 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox and failed · Nov 18, 2026 — Needs pnpm, npm cannot install it · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.