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:
Install
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://github.com/shadcn-ui/ui/blob/main/skills/migrate-radix-to-base/SKILL.md 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 and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.