shadcn/ui Skills: official rules for shadcn components
shadcn-ui/ui
Two playbooks from the shadcn/ui team for your AI coding assistant. The main one makes it build screens from the ready-made shadcn/ui parts in the way the team intends. The second moves an app from one set of building blocks (Radix) to another (Base UI), one piece at a time.
Pack description by its author: “Two playbooks from the shadcn/ui team for your AI coding assistant. The main one makes it build screens from the ready-made shadcn/ui parts in the way the team intends. The second moves an app from one set of building blocks (Radix) to another (Base UI), one piece at a time.”
Design and frontendKnowledge and rules for your assistantGives your assistant new abilities with scripts
1. Changes your files
Skills that write or edit files: shadcn, migrate-radix-to-base.
github.com/shadcn-ui/ui/blob/8f04138/2. Runs code on your machine
Install: Markdown files, two small PNG icons, three showcase helper files and one Node script are copied. No hooks, no install scripts. Every time the shadcn skill loads (Claude Code): Runs npx shadcn@latest info --json in your project and pastes the result into the assistant's context. npx downloads the latest shadcn package from npm if it is not cached.
github.com/shadcn-ui/ui/blob/8f04138/3. Sends data
The skills always call shadcn@latest, so what runs is whatever version npm serves that day, with no pinned version. Components from community registries are third-party code added to your project; read them before you keep them. Install the skills only from github.com/shadcn-ui/ui.
github.com/shadcn-ui/ui/blob/8f04138/4. Commercial use
MIT: keep the license notice; components from community registries carry their own licenses
github.com/shadcn-ui/ui/blob/8f04138/Checked against the pack's files at commit 8f04138, on Oct 28, 2026. Tap a verdict to see its source.How we checkedReport an error
The pack has changed since AgentGid checked it on Oct 28, 2026. Some details may be out of date.
Good for you if
- You build a site or app with shadcn/ui and use Claude Code, Cursor, Codex or another assistant that reads skills
- You want it to add forms, dashboards, settings pages or chat screens with the right parts, not hand-made copies
- You have a brand or style guide (a DESIGN.md) and want an app and a design system page themed from it
- Your shadcn/ui app is built on Radix and you want to switch it to Base UI without losing your own changes
Probably not for you if
- You don't use shadcn/ui: both skills are about shadcn/ui projects only
- You want no tools downloaded while your assistant works: the main skill runs the shadcn tool fresh from the internet each time
What its answer looks like
Prompts from the official docs
The shadcn/ui Skills page lists ready prompts: a login form, a settings page, a dashboard, switching to a preset code, adding a hero from @tailark.
The skill's own example, from apps/v4/content/docs/(root)/skills.mdx. More examples
What you'll notice
- Your assistant looks up your project settings first: icon set, folders, style, Tailwind version
- It asks which component source to use before adding a block, and asks before overwriting your files
- New components land in your project as code you own, then your assistant reads them over and fixes imports
- During a Radix to Base UI move: a new branch, one save point per component and a short report per component in .migration/
What you need
- Claude Code, Cursor, any agent that supports skills
- Free, MIT license
- One command: npx skills add shadcn/ui
- Needs Node.js, because the skills run the shadcn tool through npx. Private component sources may need your own token.
Words on this page
- Skill
- A set of written instructions your AI assistant follows. Installing one is like giving it a playbook.
- Plugin
- A package your assistant installs that can bring skills, commands and hooks together.
- MCP
- A standard way to connect an AI assistant to outside tools and data.
| Repository | shadcn-ui/ui · website |
|---|---|
| GitHub stars | 128,719 (the shadcn/ui repository: these skills ship inside the product, so the stars are the product's) |
| Skills | 2 · 1 with scripts |
| Category | Design and frontend |
| License | MIT |
| Last updated | Nov 21, 2026 · card checked Oct 28, 2026 at commit 8f04138 |
| Install counts | shadcn-ui/ui on skills.sh, Vercel's skills directory, which shows installs and security audits per skill |
shadcn-ui/ui popularity over time
What shadcn/ui Skills does
- Reads your project's shadcn setup (components.json) through the shadcn tool and puts it in front of the assistant
- Use existing components first: search the component sources before writing custom screens
- Compose, don't reinvent: a settings page is Tabs + Card + form parts, a dashboard is Sidebar + Card + Chart + Table
- Built-in variants before custom styles, and theme colours (bg-primary) instead of raw ones (bg-blue-500)
- Always looks up a component's docs and examples before creating or fixing it
- Updates components from upstream by previewing each change and keeping your own edits
- Turns a DESIGN.md into a themed app plus a design system page, then checks it in a browser
- Moves Radix components to Base UI one at a time, keeping the app building at every step
Never cut, per the skill: your local changes to components (merged, not overwritten), and your yes before --overwrite or before switching presets.
From the pack's SKILL.md files, summarised by AgentGid.
The 2 skills, explained
shadcn
Builds and fixes screens with the right shadcn/ui parts, themes them, and adds new parts to your project
You give
- A shadcn/ui project (or a request to create one with a preset code or style name)
- Which component source to use when you ask for a block
- For a design system: a DESIGN.md file, and optionally a preset code
You get
- Components added as code in your project, read over and fixed after adding
- Forms, overlays, cards, icons and chat screens built to the team's rules
- Preset switches done the way you choose: overwrite, partial, merge or skip
- From a DESIGN.md: a themed app, a design system page and a report of what maps where and contrast pairs under 4.5:1
migrate-radix-to-base
Moves your app's parts from Radix to Base UI, one component at a time, and keeps your own tweaks
You give
- A shadcn or other React project on Radix, with no unsaved changes in git
- One component to move, or a clear ask for the whole project
You get
- A new branch with one save point per component
- The moved component, with your customizations carried over
- A report per component in .migration/: Changed, Left alone, Behavior changes, Verify by hand
- A count at the end of how many components are still on Radix
Its rules, in pictures
The page it plans
Drawn by AgentGid from the values in the skill's files. This is not output of the skill; sample text is ours.
See it in action
The skill defines what its answer looks like. Its own example:
# <component> <date, strategy used, one-line verdict> ## Changed ## Left alone ## Behavior changes ## Verify by hand
The skill defines what its answer looks like. Its own example:
The shadcn/ui Skills page lists ready prompts: a login form, a settings page, a dashboard, switching to a preset code, adding a hero from @tailark.
The skill defines what its answer looks like. Its own example:
<FieldGroup>
<Field>
<FieldLabel htmlFor="email">Email</FieldLabel>
<Input id="email" />
</Field>
</FieldGroup>
From skills/shadcn/SKILL.md.
When to reach for it
| You want | Use |
|---|---|
| Your assistant should build screens from shadcn/ui parts | shadcn (loads by itself in a shadcn project) |
| Switch your app's look to a preset code | shadcn: "Switch to --preset <code>"; it asks overwrite, partial, merge or skip |
| A themed app and design system page from a DESIGN.md | shadcn: "apply this DESIGN.md" |
| Update a component and keep your edits | shadcn (preview with --dry-run and --diff, merge per file) |
| Move one component from Radix to Base UI | migrate-radix-to-base: "migrate accordion to base-ui" |
| Move the whole app to Base UI | migrate-radix-to-base, asked explicitly for the whole project |
Skills in shadcn-ui/ui
| Skill | In plain words | Changes files? | What it does (author) |
|---|---|---|---|
| migrate-radix-to-base | Moves your app's parts from Radix to Base UI, one component at a time, and keeps your own tweaks | Yes | Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.npx skills add shadcn-ui/ui --skill migrate-radix-to-base |
| shadcn | Builds and fixes screens with the right shadcn/ui parts, themes them, and adds new parts to your project | Yes | Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with… has scriptsnpx skills add shadcn-ui/ui --skill shadcn |
The author's descriptions come from each skill's SKILL.md; the plain-words column is AgentGid's.
Good to know before you install
- The main skill switches on by itself in any project with a components.json file. In Claude Code it runs npx shadcn@latest info --json as it loads, so the newest shadcn tool is downloaded and run each time.
- It pre-approves shadcn commands for your assistant (npx, pnpm dlx or bunx shadcn@latest), so those run without a permission prompt in hosts that honour allowed-tools. These commands add, overwrite and restyle files in your project.
- Community component sources are other people's code that lands in your project. The skill tells your assistant to ask which source to use and to read every added file.
- The Base UI move makes git save points and a branch on its own, installs @base-ui/react, and removes the Radix packages after the last component. It needs a clean git tree first.
- Behaviour that differs between Radix and Base UI (tabs, menu closing, a navigation delay) is flagged in the report, not quietly changed. Check the Verify by hand list yourself.
- The Cursor plugin manifest also starts the shadcn MCP server (npx shadcn@latest mcp), which lets the assistant search and install components from component sources.
Before you start
Works in
- Any agent with a skills folder: skills CLI
- Claude Code: skills folder
- Cursor: plugin
- Codex: skills folder (agents/openai.yml metadata); MCP server by manual config
- OpenCode: MCP server
You will need
- Node.js package runner (npx, pnpm dlx or bunx): Every skill action runs the shadcn CLI through it
- A shadcn/ui project (components.json): The skill activates only in such a project
- git: migrate-radix-to-base needs a clean tree, a branch and per-component commits
Steps only you can do
- Pick the component source when asked, and answer overwrite, partial, merge or skip when switching presets (skills/shadcn/SKILL.md (Workflow))
Then: The assistant adds the block or applies the preset the way you chose - For a private registry, put your token in an environment variable yourself (never in components.json) (skills/shadcn/mcp.md (registries))
Then: The assistant adds the registry to components.json with a ${VAR} reference - For Codex, add the shadcn MCP server to ~/.codex/config.toml by hand (optional) (skills/shadcn/mcp.md (Setup))
Then: Codex can search and install registry items through MCP - After a Base UI move, check the behaviour changes listed in the report (.migration/<component>.md in your project)
Then: You decide whether to keep or change the Base UI behaviour
Mistakes to avoid
Say "add a login block" and let the assistant pick a component source
Name the source in the request (@shadcn, @tailark, owner/repo)
The skill tells the assistant to ask instead of guessing; community sources are other people's code that lands in your projectUpdate customized components with --overwrite to get the upstream version
Preview with --dry-run and --diff, merge per file, and use --overwrite only after an explicit yes
--overwrite replaces your local edits to the component filesCompare presets in a scratch folder without passing the base library
Run preset commands inside the project, or pass --base with the project's current base in a scratch folder
A preset code does not say whether the project is on Radix or Base UIStart the Radix to Base UI move with uncommitted changes in the project
Commit or stash first; the skill works on a branch with one commit per component
The migration needs a clean git tree to keep one save point per componentExpect the shadcn MCP server to tell the assistant the project's aliases and Tailwind version
Keep the skill (it runs shadcn info) and use the MCP server only for searching and installing registry items
The MCP tools cover registry work only
Which one to pick
| If you need | Pick |
|---|---|
| You build with shadcn/ui and want the assistant to use its components, presets and CLI the way the shadcn team intends | This pack |
| You want design commands to polish, critique and audit any UI, not tied to one component library | pbakaus/impeccable |
| You want a design skill aimed at avoiding generic AI-looking UI in Claude Code, Cursor or Codex | Nutlope/hallmark |
Works well with
- shadcn: The skills drive the shadcn command-line tool for every action
- base-ui-react: migrate-radix-to-base moves components to @base-ui/react
- claude-code: In Claude Code the skill injects the project's shadcn info as it loads
- cursor: The repo ships a Cursor plugin manifest with the skills and the shadcn MCP server
May I use it like this?
| Use | Answer | Condition |
|---|---|---|
| In a commercial app | Yes | MIT: keep the license notice; components from community registries carry their own licenses |
| Passing the files on | Yes | MIT: keep the copyright and permission notice in copies |
| Work for clients | Yes | MIT allows use in work for others |
| Shipped inside your app | Yes | MIT: keep the license notice |
What leaves your machine
- A download request for the shadcn package (latest version) → The npm registry, through npx, pnpm dlx or bunx, Each time the skill loads in Claude Code, and on shadcn commands when the package is not cached. Opt out: No opt-out inside the skill; it always calls shadcn@latest
- Component names, search queries and docs lookups → ui.shadcn.com, raw.githubusercontent.com and any component registries you use, On search, view, docs and add. Opt out: Do not ask for registry or docs lookups
- An Authorization header with a token from your environment → A private registry you configure in components.json, On requests to that registry. Opt out: Do not configure headers for registries
- Your components.json style name and component names in fetch URLs → ui.shadcn.com/r/styles/..., During the Radix to Base UI move. Opt out: Do not run migrate-radix-to-base
Install shadcn/ui Skills
Official commands from the repository
npx skills add shadcn/ui
Official command from the shadcn/ui docs (ui.shadcn.com/docs/skills). Installs both skills from skills/.
The repo ships .cursor-plugin/plugin.json, which points at ./skills/ and adds the shadcn MCP server. The repo gives no install command for it.
npx shadcn@latest mcp init
Not a skill: writes the MCP server config for your editor (.mcp.json for Claude Code, .cursor/mcp.json, .vscode/mcp.json). Codex needs a manual edit of ~/.codex/config.toml.
Or with the open-source skills CLI: npx skills add shadcn-ui/ui. Skills are instructions your agent follows: read them before installing.
What it installs and runs on your machine
Read in the code at commit 8f04138, Oct 28, 2026
| When | What happens |
|---|---|
| Install | Markdown files, two small PNG icons, three showcase helper files and one Node script are copied. No hooks, no install scripts. |
| Every time the shadcn skill loads (Claude Code) | Runs npx shadcn@latest info --json in your project and pastes the result into the assistant's context. npx downloads the latest shadcn package from npm if it is not cached. |
| shadcn skill at work | Your assistant runs shadcn commands: init, add, apply, search, view, docs. They write component files, components.json and your CSS file, and install packages. search, view, docs and add fetch from ui.shadcn.com, configured registries and public GitHub registries. |
| shadcn skill at work (docs) | It tells your assistant to fetch the docs and example URLs that shadcn docs prints (ui.shadcn.com and raw.githubusercontent.com). |
| Private registries | Registry entries in components.json can send an Authorization header filled from your environment variables. |
| Design system from DESIGN.md | Scaffolds a new app, installs every component and Fontsource fonts with your package manager, starts the dev server and checks it in a browser. showcase-coverage.mjs only reads local files and prints which components the page does not show; no network, no writes. |
| migrate-radix-to-base | Runs shadcn info, your typecheck and build, installs @base-ui/react, fetches stock component files from ui.shadcn.com/r/styles/..., makes a branch and one git commit per component, writes reports to .migration/ in your project, and edits components.json. |
| Cursor plugin | The manifest declares an MCP server started with npx shadcn@latest mcp (downloaded from npm). |
| Rest of the repo | The shadcn/ui product itself (website, the shadcn command-line tool in packages/, tests) is not part of the skills and is not installed by npx skills add. The tool the skills call is that package, fetched from npm. |
The author's numbers, as reported
AgentGid did not run these tests
- Base UI migration tested on real projects: 60+ components, 36 on Radix; a full migration took about 25 minutes at roughly 10k tokens per component (Team's own runs, described in the July 2026 changelog; no files or numbers per project in the repo). Source
Settings
components.json registries: Named component sources (@name -> URL with {name}); headers may use ${VAR} from your environment--only theme,font: Partial preset switch: theme and fonts only, components untouched
Quick answers
- Is it free?
- Yes. The repo is under the MIT license.
- Do I have to call it?
- No. The shadcn skill is not a slash command; it loads when your project has a components.json file.
- Does it send anything over the internet?
- Yes. It runs the shadcn tool through npx, which comes from npm, and it fetches component files and docs from ui.shadcn.com, GitHub and any registries you add.
- Will it overwrite my customized components?
- Not without your yes. Updates are previewed per file and merged; --overwrite needs your explicit approval.
- Can I stop a Base UI move halfway?
- Yes. Progress lives in your files: the next run finds the half-done component and resumes.
- Does the migration touch libraries that are not Radix?
- No. cmdk, vaul, sonner, input-otp, react-day-picker and recharts are left alone and listed in the report.
Checked by AgentGid on Oct 28, 2026 against commit 8f04138 of the pack's own files. agent.md for AI agents · Report a mistake
More design and frontend skill packs
| # | Skill pack | Skills | GitHub stars | Updated |
|---|---|---|---|---|
| 1 |
nextlevelbuilder/ui-ux-pro-max-skill Your AI assistant gets a local design library: UI styles, colour palettes, font pairings and UX rules for many product types. Bef…
|
7 | 153K | 2026-11-22 |
| 2 |
Leonxlnx/taste-skill Your AI coding assistant stops building the average landing page. It picks one of 20 researched design directions, finds real, cr…
|
1 | 120K | 2026-11-22 |
| 3 |
tt-a1i/archify Your AI assistant turns a description, a Mermaid sketch or your project's code into an interactive diagram saved as one HTML file…
|
5 | 98.7K | 2026-11-22 |
| 4 |
cathrynlavery/diagram-design Your AI assistant draws clean, editorial diagrams in your brand colours and fonts. You describe the diagram in plain words and ge…
|
1 | 70K | 2026-11-22 |
| 5 |
Nutlope/hallmark Your AI assistant builds web pages that look designed, not machine-made. It asks once for your real material and picks one of fif…
|
1 | 59.2K | 2026-11-11 |
| 6 |
alchaincyf/huashu-design One large design playbook for your AI assistant, written in Chinese. It makes clickable app prototypes, web pages, slide decks, i…
|
1 | 30.3K | 2026-11-22 |