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.
What this skill does
# 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/vite` or `@tailwindcss/postcss`. No `tailwind.config.js`. See the tailwind-css skill.
- **Path alias** `@/*` → `./src/*` (or your source root) in `tsconfig` and in the bundler (e.g. Vite `resolve.alias`).
- **React** (Next.js App Router, Vite, etc.).
---
## Installation
Reference: [Official installation guide](https://ui.shadcn.com/docs/installation)
### 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](https://ui.shadcn.com/docs/installation)). Choose framework (Next.js, Vite, etc.), style (new-york recommended), base color, and CSS variables.
### Existing project (Next.js App Router)
1. **Init** — creates `components.json`, optional `cn` helper and base styles. Run: `shadcn init` (invoke via package manager; see docs above).
2. **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/postcss` in `postcss.config.mjs`. Do not add `tailwind.config.js`.
3. **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") }` in `vite.config.ts`; add `@types/node` if using `path`.
- Tailwind: `@tailwindcss/vite` in 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`):
```tsx
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 `className` and spread props; use Tailwind classes and the **`cn()`** 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 variRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.