Skip to content
ReviewRamble

The weekly brief

AI, reviewed, in your inbox.

  • New reviews of tools, models, MCP servers and repos, with the verdict up front
  • Re-checked prices and ratings when something changes
  • New analysis pieces as they are published

Models, agents, MCP servers and the tools actually worth your time.

One email a week. Unsubscribe with the link in any brief. How we use your email

shadcn/ui

React components you copy into your own code, now with an agent skill that teaches Claude Code, Codex and Cursor to use them properly.

Reviewed by ReviewRamble editors · Updated

View on GitHub Open source

Share this page:XLinkedInFacebookRedditWhatsAppEmail

Our rating

4.5/5

Still the default way to give a React app a component layer you own, and its agent skill is the clearest example yet of a library teaching coding agents its own rules.

What is shadcn/ui?

shadcn/ui is not a package you import. Its CLI copies each component's source into your project, where you own and edit it, and the same CLI pulls items from third-party and private registries. Components sit on Radix, Base UI or React Aria and are styled with Tailwind; setup guides cover Next.js, Vite, Laravel, React Router, Astro and TanStack Start.

The repository also ships agent skills: folders with a SKILL.md that a coding agent loads when the task calls for it. The main skill, shadcn, reads your components.json through `shadcn info --json` and gives the agent your framework, Tailwind version, aliases, icon library, base library and installed components, plus rules for composing them. A second skill, migrate-radix-to-base, moves a project from Radix to Base UI. You install them with Vercel's skills CLI: `npx skills add shadcn/ui`.

The repository was created in January 2023 and has about 128,470 stars and 11,417 forks. The CLI's latest release is shadcn@4.23.0 (27 October 2026), and the most recent commit landed on 17 November 2026.

Is shadcn/ui worth it?

The skill matters more than it first looks, because shadcn/ui is the library coding agents already reach for and most often get subtly wrong. An agent writing from training data will stack form fields in a div with space-y-4, override colours with bg-blue-500 and forget the DialogTitle that screen readers need. The shadcn skill is a written rulebook against exactly those habits: forms go in FieldGroup and Field, option sets of 2 to 7 choices use ToggleGroup, colours come from semantic tokens, and every Dialog, Sheet and Drawer gets a title. Each rule links to a file of incorrect and correct pairs.

The second half is project context. When the skill loads, it runs `shadcn info --json` and hands the agent your real configuration, including whether the project uses Radix, Base UI or React Aria, which changes the API for custom triggers. It then steers the agent to `shadcn search`, `shadcn docs` and `add --diff` before it writes anything by hand, and tells it to ask which registry to use rather than guess. The skill has an evals file with 8 test prompts, which is more discipline than most community skills show.

Installing is one command, `npx skills add shadcn/ui`, run from your project. Vercel's skills CLI detects which agents you have (it lists Claude Code, Codex, Cursor, OpenCode and 75 more) and asks where to put the files; add -g to install across projects. On skills.sh the shadcn skill shows about 152,400 installs and the migration skill about 38,500. The docs describe the experience in Claude Code; the repo also carries a small agents/openai.yml so the skill shows a name and icon in Codex. The separate MCP server, set up with `npx shadcn@latest mcp init --client claude` (or cursor, vscode, codex, opencode), lets the agent browse and install from registries; the skill tells it how to use that server too.

The security trade-off is specific. The skill pre-approves shell commands that run `shadcn@latest` through npx, pnpm dlx or bunx, so in Claude Code the agent can run the CLI, including add, without asking, and @latest means whatever version npm serves that day. Components from community registries arrive as source in your tree; the skill tells the agent to read them afterwards, which is advice, not a check. The skills CLI sends anonymous install telemetry unless you set DISABLE_TELEMETRY=1.

As a library, the model holds up after nearly four years: you get readable code and no lock-in, and you pay for it in upkeep, because copied components do not update themselves. The 1,746 open issues and pull requests show how much traffic the project carries. For a React team using agents, the skill is cheap to add and corrects the mistakes agents make most often in this codebase; for anyone not on shadcn/ui, it does nothing.

Where it earns its place

  • A solo founder building a SaaS dashboard in Next.js with Claude Code

    Get a settings page and data table that look consistent without hand-fixing every form

    Run `npx skills add shadcn/ui` once, then ask for the page. The agent reads the project config, adds Tabs, Card and form components through the CLI and follows the FieldGroup rules. No cost beyond normal model usage.

  • A front-end lead at a 20-person product team with an internal component registry

    Make agents pull our branded components instead of inventing new ones

    Add the private registry to components.json with its auth variables in .env.local, install the skill and the MCP server, and agents search the registry before writing markup. The skill's rule to ask which registry to use keeps them from defaulting to public items.

  • A team on an older shadcn/ui project built on Radix

    Move to Base UI without breaking the build

    The migrate-radix-to-base skill checks the base library with `shadcn info`, asks for a clean git tree, runs your typecheck first and migrates one component per commit, keeping Radix installed until the last one moves.

Before you commit

Setup
Initialise a project with `npx shadcn@latest init` (or a template), then `npx skills add shadcn/ui` from the project root; the skills CLI needs Node.js 22.20 or later. Optional MCP server: `npx shadcn@latest mcp init --client <agent>`; Codex needs its config.toml edited by hand.
Integrations
Skills install through Vercel's skills CLI for Claude Code, Codex, Cursor, OpenCode and other agents. MCP server for Claude Code, Cursor, VS Code with Copilot, Codex and OpenCode. Registries: the official one, community registries and private ones with authentication.
Data and privacy
A front-end library with no hosted service. The skill runs the shadcn CLI locally; the skills CLI sends anonymous install telemetry (DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 turns it off). Private registry tokens sit in your .env.local.
Cost at scale
Free at any size. The real cost is maintenance of copied components and the context the skill adds each time it loads; token usage per load is not published.
Limits
React only, built around Tailwind. The skill is triggered by a components.json file, so it does nothing in projects without one. The docs show the flow in Claude Code; how other agents handle the skill's inline `shadcn info` command is not documented.

What’s good

  • Component source lives in your repo, with no runtime dependency to fight
  • Skill reads the real project config before the agent writes code
  • Concrete composition rules with incorrect and correct examples
  • One install command covers Claude Code, Codex, Cursor and dozens more agents
  • MIT licence; skills, CLI and MCP server are free

What’s not

  • Skill pre-approves unpinned `npx shadcn@latest` commands
  • Copied components need manual updates
  • Third-party registry code is reviewed only by the agent, if at all
  • React and Tailwind only

Best for

React and Tailwind teams who let coding agents build UI and want the output to follow shadcn/ui's own conventions.

shadcn/ui alternatives

shadcn/ui: common questions

Is shadcn/ui worth it?
Still the default way to give a React app a component layer you own, and its agent skill is the clearest example yet of a library teaching coding agents its own rules. We rate it 4.5 out of 5.
How much does shadcn/ui cost?
Free under the MIT licence; no paid tier. The skills are free too.
What are the downsides of shadcn/ui?
Skill pre-approves unpinned `npx shadcn@latest` commands; copied components need manual updates; third-party registry code is reviewed only by the agent, if at all; react and Tailwind only.
Who is shadcn/ui best for?
React and Tailwind teams who let coding agents build UI and want the output to follow shadcn/ui's own conventions.
How much does shadcn/ui cost for a team or in production?
Free at any size. The real cost is maintenance of copied components and the context the skill adds each time it loads; token usage per load is not published.
Is shadcn/ui safe for company data?
A front-end library with no hosted service. The skill runs the shadcn CLI locally; the skills CLI sends anonymous install telemetry (DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1 turns it off). Private registry tokens sit in your .env.local.
What are the best shadcn/ui alternatives?
The closest alternatives we have reviewed are Astryx, Impeccable and Anthropic Skills.

Answers checked Nov 18, 2026.

Make shadcn/ui? Show this rating on your siteshadcn/ui rated 4.5 out of 5 on ReviewRamble