shadcn-dev
This skill should be used when the user asks to "set up shadcn", "configure shadcn", "shadcn project setup", "install shadcn", "shadcn init", "ui components for react", or mentions general shadcn/ui configuration questions. For specific topics like theming, forms, or data tables, focused skills may be more appropriate.
What this skill does
# shadcn/ui Development
Configure and build React applications with shadcn/ui components and Tailwind CSS v4.
## shadcn/ui Overview
shadcn/ui is not a component library - it's a collection of reusable components that are copied directly into projects. Components are:
- **Accessible**: Built on Radix UI primitives
- **Customizable**: Full source code ownership
- **Composable**: Combine components freely
- **Framework-agnostic**: Works with Next.js, Vite, TanStack Start, Remix, Astro, Expo
## Installation
### Initialize shadcn/ui
```bash
npx shadcn@latest init
```
Configuration prompts:
- Style (New York or Default)
- Base color
- CSS variables for colors
- Global CSS file location
- Tailwind config location
- Component import alias (@/components)
- Utility import alias (@/lib/utils)
### Add Components
```bash
# Single component
npx shadcn@latest add button
# Multiple components
npx shadcn@latest add button card dialog
# All components
npx shadcn@latest add --all
```
## Project Structure
After initialization:
```
project/
├── components/
│ └── ui/ # shadcn components
│ ├── button.tsx
│ ├── card.tsx
│ └── ...
├── lib/
│ └── utils.ts # cn() utility
├── components.json # shadcn config
└── app/
└── globals.css # CSS variables + Tailwind
```
## The cn() Utility
Located in `lib/utils.ts`, combines clsx and tailwind-merge:
```typescript
import { clsx, type ClassValue } from "clsx"
import { twMerge } from "tailwind-merge"
export function cn(...inputs: ClassValue[]) {
return twMerge(clsx(inputs))
}
```
Use for conditional and merged class names:
```tsx
<Button className={cn("w-full", isLoading && "opacity-50")} />
```
## Focused Skills
For specific topics, use these focused skills:
| Topic | Skill | Trigger Phrases |
|-------|-------|-----------------|
| Component Usage | `/shadcn-dev:shadcn-components` | "add button", "dialog component", "card usage" |
| Theming | `/shadcn-dev:shadcn-theming` | "dark mode", "custom colors", "css variables" |
| Forms | `/shadcn-dev:shadcn-forms` | "form validation", "react-hook-form", "zod" |
| Data Tables | `/shadcn-dev:shadcn-data-tables` | "data table", "tanstack table", "sortable" |
| Tailwind v4 | `/shadcn-dev:tailwindv4` | "tailwind v4", "@theme", "css-first config" |
## Troubleshooting
For debugging issues, the shadcn-troubleshoot agent can autonomously diagnose and fix common problems including:
- Component import errors
- Styling conflicts
- Hydration mismatches
- Missing dependencies
## Framework-Specific Setup
### Next.js (App Router)
```bash
npx create-next-app@latest my-app --typescript --tailwind
cd my-app
npx shadcn@latest init
```
### Vite
```bash
npm create vite@latest my-app -- --template react-ts
cd my-app
npm install -D tailwindcss postcss autoprefixer
npx tailwindcss init -p
npx shadcn@latest init
```
### TanStack Start
```bash
npx create-tanstack-start my-app
cd my-app
npx shadcn@latest init
```
### Expo (React Native Web)
See the Expo-specific setup guide in shadcn docs for React Native Web integration.
## Key Dependencies
shadcn/ui components typically require:
- `tailwindcss` - Styling
- `@radix-ui/*` - Accessible primitives
- `class-variance-authority` - Variant management
- `clsx` - Conditional classes
- `tailwind-merge` - Class deduplication
- `lucide-react` - Icons
## Reference Files
- **`references/community-repositories.md`** - Top 10 community repos for learning
- **`references/component-patterns.md`** - Common composition patterns
## Resources
- Official docs: https://ui.shadcn.com
- GitHub: https://github.com/shadcn-ui/ui
- Components: https://ui.shadcn.com/docs/components
Related 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.