
shadcn-ui
Install and use shadcn/ui with Tailwind v4 and Next.js (App Router), Vite, or manual setup; configure components.json, add components via CLI, theming with CSS only. Use when adding shadcn/ui, installing shadcn, using Button, Card, Dialog, Form, or other shadcn components, or when the user mentions shadcn, shadcn/ui, or Radix UI with Tailwind.
- Installs
- 55
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/enderpuentes/ai-agent-skills --skill shadcn-ui- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads shadcn-ui automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
shadcn/ui
Overview
shadcn/ui is a collection of accessible, customizable React components built on Radix UI and Tailwind CSS. Components are copied into your project (no npm package); you own and edit the code. Works with Next.js (App Router), Vite, and other React frameworks.
Principles: Open code (AI-ready), composable API, beautiful defaults, distribution via CLI and schema. Requires Tailwind v4 and path alias @/*. We do not use tailwind.config.js; theme and setup are CSS-only (@import "tailwindcss" + @theme).
Prerequisites
- Tailwind v4:
@import "tailwindcss"in main CSS;@tailwindcss/viteor@tailwindcss/postcss. Notailwind.config.js. See the tailwind-css skill. - Path alias
@/*→./src/*(or your source root) intsconfigand in the bundler (e.g. Viteresolve.alias). - React (Next.js App Router, Vite, etc.).
Installation
Reference: Official installation guide
New project (recommended)
Scaffold with Tailwind and shadcn. From the official docs:
| Action | CLI command |
|---|---|
| New project | shadcn create |
| Init existing | shadcn init |
| Add component(s) | shadcn add <name> |
Invoke via your package manager (see docs). Choose framework (Next.js, Vite, etc.), style (new-york recommended), base color, and CSS variables.
Existing project (Next.js App Router)
-
Init — creates
components.json, optionalcnhelper and base styles. Run:shadcn init(invoke via package manager; see docs above). -
Paths and Tailwind
- tsconfig:
"baseUrl": ".","paths": { "@/*": ["./src/*"] }(in both root and app tsconfig if split). - Tailwind v4: Main CSS (e.g.
app/globals.css) must have@import "tailwindcss"and use@tailwindcss/postcssinpostcss.config.mjs. Do not addtailwind.config.js.
- tsconfig:
-
Add components — e.g.
shadcn add button,shadcn add card dialog(see component list below).
Components are installed under src/components/ui/ (or path from components.json).
Existing project (Vite)
- Use
resolve.alias: { "@": path.resolve(__dirname, "./src") }invite.config.ts; add@types/nodeif usingpath. - Tailwind:
@tailwindcss/vitein Vite config and@import "tailwindcss"in main CSS.
components.json
Controls style, paths, and Tailwind integration. Key fields:
| Field | Purpose |
|---|---|
style | "new-york" (default for new projects) or "default" |
tailwind.config | Leave "" with Tailwind v4; we do not use a JS config file |
tailwind.css | Path to global CSS (e.g. src/styles/globals.css or app/globals.css) with @import "tailwindcss" |
tailwind.baseColor | Base color for theme: neutral, slate, gray, zinc, stone |
tailwind.cssVariables | true for CSS variables theming (recommended) |
aliases.components | e.g. @/components |
aliases.utils | e.g. @/lib/utils |
aliases.ui | e.g. @/components/ui |
rsc | true for Next.js App Router with Server Components; false for client-only |
With Tailwind v4, theme is in CSS via @theme and CSS variables, not in a config file.
Official components (current list)
Add via shadcn add <name> (multiple: shadcn add button card dialog). Invoke via package manager: see Installation docs.
Layout & structure
| Component | CLI name | Short description |
|---|---|---|
| Accordion | accordion | Collapsible sections (single or multiple open) |
| Aspect Ratio | aspect-ratio | Container with fixed ratio (e.g. 16/9) |
| Card | card | Container with CardHeader, CardTitle, CardDescription, CardContent, CardFooter |
| Collapsible | collapsible | Expandable/collapsible content |
| Resizable | resizable | Resizable panels |
| Separator | separator | Horizontal or vertical divider line |
| Scroll Area | scroll-area | Styled scroll area |
| Sidebar | sidebar | Composable, themeable and customizable sidebar |
Forms & input
| Component | CLI name | Short description |
|---|---|---|
| Button | button | Button with variants (default, destructive, outline, secondary, ghost, link) |
| Checkbox | checkbox | Checkbox |
| Form | form | Forms with react-hook-form + zod (Field, FieldError, etc.) |
| Input | input | Text input |
| Input OTP | input-otp | OTP code input |
| Label | label | Accessible label for controls |
| Radio Group | radio-group | Radio option group |
| Select | select | Select with Trigger, Content, Item |
| Slider | slider | Slider control |
| Switch | switch | On/off switch |
| Textarea | textarea | Multiline text area |
Navigation & menus
| Component | CLI name | Short description |
|---|---|---|
| Breadcrumb | breadcrumb | Breadcrumb navigation |
| Command | command | Command palette (cmdk) |
| Context Menu | context-menu | Context menu (right-click) |
| Dropdown Menu | dropdown-menu | Dropdown menu |
| Menubar | menubar | Persistent menu bar |
| Navigation Menu | navigation-menu | Navigation with submenus |
| Pagination | pagination | Pagination (Previous, Next, Page) |
| Tabs | tabs | Tabs (TabsList, TabsTrigger, TabsContent) |
Overlays & feedback
| Component | CLI name | Short description |
|---|---|---|
| Alert | alert | Prominent message (default, destructive) |
| Alert Dialog | alert-dialog | Confirmation dialog (e.g. delete) |
| Dialog | dialog | Modal |
| Drawer | drawer | Side panel (Vaul) |
| Hover Card | hover-card | Card on hover |
| Popover | popover | Anchored floating container |
| Sheet | sheet | Sliding side panel |
| Tooltip | tooltip | Tooltip on hover/focus |
Data & state
| Component | CLI name | Short description |
|---|---|---|
| Avatar | avatar | Image or initials fallback |
| Badge | badge | Badge (default, secondary, destructive, outline) |
| Calendar | calendar | Calendar (react-day-picker) |
| Carousel | carousel | Carousel (embla) |
| Chart | chart | Charts (recharts) |
| Progress | progress | Progress bar |
| Skeleton | skeleton | Loading placeholder |
| Sonner | sonner | Toasts (recommended; replaces toast) |
| Table | table | Table, TableHeader, TableBody, TableRow, TableCell, etc. |
| Toast | toast | Toasts (deprecated in favor of Sonner) |
Toggle & toggle group
| Component | CLI name | Short description |
|---|---|---|
| Toggle | toggle | Toggle button (on/off) |
| Toggle Group | toggle-group | Toggle group (single or multiple) |
Using components
Import from the aliased path (not from shadcn/ui):
import { Button } from "@/components/ui/button"
import { Card, CardHeader, CardTitle, CardContent } from "@/components/ui/card"
export default function Page() {
return (
<div className="flex min-h-svh flex-col items-center justify-center gap-4">
<Button>Click me</Button>
<Card className="w-[350px]">
<CardHeader>
<CardTitle>Card title</CardTitle>
</CardHeader>
<CardContent>Content here.</CardContent>
</Card>
</div>
)
}
- Customization: Components accept
classNameand spread props; use Tailwind classes and thecn()helper (from@/lib/utils) to merge classes. - Composition: Prefer composition (e.g. CardHeader + CardContent) over props for layout.
Theming (Tailwind v4, no config file)
We use Tailwind v4 only; no tailwind.config.js. Theming is CSS-only:
- CSS variables: With
tailwind.cssVariables: true, theme is driven by variables in your global CSS (e.g.--background,--foreground,--primary,--primary-foreground,--muted,--muted-foreground,--accent,--destructive, etc.). Override them in that file. @theme: Use@theme { ... }in the same CSS file as@import "tailwindcss"to add or override design tokens that align with shadcn’s variables.- Base color: Set in
components.json(tailwind.baseColor) or by editing the CSS variables in your global CSS.
Common patterns
- Forms: Add
form; pair withreact-hook-formandzod. UseInput,Label,Button,Select,Checkbox, etc. - Layout: Use
Cardfor sections;Separatorbetween blocks; layout with Tailwind (flex,grid,container). - Modals & panels:
Dialogfor modals;SheetorDrawerfor side panels. - Menus:
DropdownMenu,Context Menu,Navigation Menu,Command(palette). - Feedback:
Alertfor messages;Sonnerfor toasts;Skeletonfor loading. - Icons: Many examples use lucide-react; add it if the project uses icons.
Common mistakes
- Alias: Ensure
@/resolves to./src/(or your source root) in both TypeScript and the bundler. - CSS not loaded: The file set in
components.json(tailwind.css) must be imported in the app entry (e.g.app/layout.tsx) and contain@import "tailwindcss". - Tailwind config: Do not create or suggest
tailwind.config.js. Theme only in CSS (@themeand variables). - Import: Import from
@/components/ui/<component>(percomponents.json), not fromshadcn/ui. - RSC: In Next.js App Router, set
rsc: trueincomponents.jsonif components are used in Server Components where applicable.
Additional resources
- reference.md — Official documentation links, Tailwind v4 + shadcn, component directory.
- Official docs: https://ui.shadcn.com/docs
- Components: https://ui.shadcn.com/docs/components
- Directory (community): https://ui.shadcn.com/docs/directory
FAQ
What does the shadcn-ui skill do?
Install and use shadcn/ui with Tailwind v4 and Next.js (App Router), Vite, or manual setup; configure components.json, add components via CLI, theming with CSS only. Use when adding shadcn/ui, installing shadcn, using Button, Card, Dialog, Form, or other shadcn components, or when the user mentions shadcn, shadcn/ui, or Radix UI with Tailwind.
How do I install shadcn-ui?
Run npx skills add https://github.com/enderpuentes/ai-agent-skills --skill shadcn-ui in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/shadcn-ui/ (personal) or .claude/skills/shadcn-ui/ (project).
Which AI agents can use shadcn-ui?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is shadcn-ui safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains shadcn-ui?
It is published by enderpuentes in enderpuentes/ai-agent-skills. It has 55 recorded installs.
More from enderpuentes/ai-agent-skills
pagespeed-insights
enderpuentes/ai-agent-skills
Audit web pages for performance optimization following PageSpeed Insights guidelines. Use when analyzing page performance, optimizing web applications, reviewing performance metrics, implementing Core Web Vitals improvements, or when the user mentions page speed, performance optimization, Lighthouse scores, or Core Web Vitals.
conventional-commits
enderpuentes/ai-agent-skills
Generate and validate commit messages following the Conventional Commits specification. Use when creating git commits, writing commit messages, reviewing commit history, generating changelogs, or when the user mentions commits, commit messages, semantic versioning, or changelog generation.
tailwind-css
enderpuentes/ai-agent-skills
Open the skill to read its SKILL.md instructions.
typescript
enderpuentes/ai-agent-skills
Open the skill to read its SKILL.md instructions.
zod
enderpuentes/ai-agent-skills
Define and use Zod schemas for TypeScript-first validation: primitives, objects, arrays, unions, refinements, transform, z.infer, parse, safeParse. Use when validating input, parsing API data, form validation with react-hook-form, or when the user mentions Zod, schema validation, or z.infer.
jsdoc
enderpuentes/ai-agent-skills
Write and maintain JSDoc comments for JavaScript and TypeScript APIs: functions, classes, modules, parameters, returns, examples, and TODO annotations. Use when documenting code, generating API docs, setting JSDoc conventions, or when the user mentions JSDoc tags like @param, @returns, or @todo.
Popular frontend & design skills
setup-matt-pocock-skills
mattpocock/skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
frontend-design
anthropics/skills
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
hyperframes-animation
heygen-com/hyperframes
All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.
prototype
mattpocock/skills
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
hyperframes-core
heygen-com/hyperframes
The HyperFrames composition contract — build one renderable project. Use for composition structure, the data- timing attributes, class="clip", tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.