Today, we're releasing shadcn/cli v4. It packs a ton of features: shadcn/skills, presets, dry-run, monorepo and more.

If you're using shadcn/ui with coding agents or need better control over the defaults, this is for you.

Here's everything new: First, shadcn/skills: gives coding agents the context they need to work with your components and registry. Radix and Base UI, updated APIs, component patterns and registry workflows.

Agents make fewer mistakes and produce code that matches your system and coding styles.

Introducing shadcn/create – Build your own shadcn/ui

Customize Everything. Pick your component library, icons, base color, theme, fonts and build something that doesn’t look like everything else.

Now available for Next.js, Vite, TanStack Start and v0. From the very first commit, the goal of shadcn/ui has been to give you solid defaults: spacing, color tokens, animations, accessibility, and let you take it from there.

Tweak the code. Add new components. Change the colors.

We’re making this even easier with npx shadcn create.

New components. This time it’s the boring stuff. The things we rebuild over and over. Made into components.

Button Group, Field, Input Group, Empty States, Item.

They compose beautifully and handle the common patterns we reach for every day.

Let’s take a look ⬇️ Let’s start with Button Group. Highly requested.

Perfect for action groups, split buttons, and more. Works horizontally, vertically, and you can even nest them.

Here’s the app idea. But first the problem:

- Our conversations are scattered across apps
- Answers are wall of text. You only care about 1-2 lines
- Copy-pasting useful parts is tedious
- And good luck finding where you ask what

Coppermind is a small...(continues in thread). Coppermind is a small app you open & forget. It runs in background.

Find something useful? Select. Tap Shift twice. Instantly added to a note.

(Demo showing ChatGPT on the left and Coppermind on the right)

Introducing the registry mcp. One command to make any component registry mcp-compatible.

Your Design System. Now with AI. Zero config.

We've got a lot to cover. Let's get started. ⬇️ 1/10 - Here’s a custom registry I built for testing. It has custom components, color tokens, fonts, everything you'd expect in a design system.

shadcn is the top comment here. Thank you. Here's why I call it a way to build your component library and NOT a component library.

"If you start a React project without shadcn/ui today, you will end up with shadcn/ui or something that looks like shadcn/ui"

Let's take a look ⬇️ We'll start a new project with React and Tailwind. Every React project has a button. Let's add one.

Introducing the new CLI.

Install anything from anywhere—add components, themes, hooks, functions, animations, and generated code to your apps.

This marks a major step forward in distributing code that both you and your LLMs can access and use.

Let’s take a look. First up, the CLI now has support for all major React frameworks out of the box: Next.js, Remix, Vite, and Laravel.

And when you initialize a new app, we update your existing Tailwind files instead of overriding them.

Introducing the Form component. Build accessible forms using react-hook-form and Radix UI.

◆ Composable & Accessible
◆ Validation using Zod
◆ Full control over markup
◆ Styled using Tailwind CSS
◆ Complete code examples
◆ Copy/Paste into your apps

ui.shadcn.com/examples/forms The Form components use Radix's composable API under the hood.

It works with Input, Checkbox, Radio Group, Select, Switch, Combobox…everything.

Give it a Zod schema and it will automatically handle validation and error message rendering using the <FormMessage /> component.