tailwind-shadcn-setup
Setup Tailwind CSS and shadcn/ui component library for Next.js projects. Use when configuring Tailwind CSS, installing shadcn/ui, setting up design tokens, configuring dark mode, initializing component library, or when user mentions Tailwind setup, shadcn/ui installation, component system, design system, or theming.
What this skill does
# tailwind-shadcn-setup
## Instructions
This skill provides complete setup and configuration for Tailwind CSS and shadcn/ui in Next.js projects. It covers installation, configuration, theming, dark mode, and component integration following modern best practices.
### 1. Tailwind CSS Installation
Install and configure Tailwind CSS for Next.js:
```bash
# Run automated installation script
bash ./skills/tailwind-shadcn-setup/scripts/install-tailwind.sh
# Or manually install dependencies
npm install -D tailwindcss postcss autoprefixer
npx tailwindcss init -p
```
**What This Does:**
- Installs Tailwind CSS, PostCSS, and Autoprefixer
- Creates `tailwind.config.ts` and `postcss.config.mjs`
- Configures content paths for Next.js
- Sets up CSS imports in global styles
### 2. shadcn/ui Initialization
Initialize shadcn/ui component library:
```bash
# Run automated shadcn/ui setup
bash ./skills/tailwind-shadcn-setup/scripts/init-shadcn.sh
# Or use shadcn CLI directly
npx shadcn@latest init
```
**Configuration Prompts:**
- TypeScript: Yes (recommended)
- Style: Default or New York
- Base color: Slate, Zinc, Neutral, Stone, or Gray
- CSS variables: Yes (recommended for theming)
- Tailwind config: tailwind.config.ts
- Components location: @/components
- Utils location: @/lib/utils
**What Gets Created:**
- `components.json` - shadcn/ui configuration
- `lib/utils.ts` - Utility functions (cn helper)
- `app/globals.css` - CSS variables and theme definitions
- Base component structure
### 3. Design Tokens & Theme Configuration
Configure design tokens using CSS variables:
```bash
# Apply comprehensive theme configuration
bash ./skills/tailwind-shadcn-setup/scripts/setup-theme.sh
```
**Theme Configuration Includes:**
- Primary, secondary, accent colors
- Background and foreground pairs
- Border, input, ring colors
- Muted, destructive, card, popover colors
- Chart colors (chart-1 through chart-5)
- Sidebar colors for navigation components
**Using CSS Variables Template:**
```typescript
// Copy and customize base theme
cp ./skills/tailwind-shadcn-setup/templates/globals.css app/globals.css
```
**Color System:**
- Uses OKLCH color space for better perceptual uniformity
- Separate light and dark mode definitions
- Foreground colors automatically calculated for accessibility
### 4. Dark Mode Configuration
Set up dark mode with class-based or system-based detection:
```bash
# Configure dark mode
bash ./skills/tailwind-shadcn-setup/scripts/setup-dark-mode.sh
```
**Dark Mode Strategies:**
1. **Class-based** (Recommended): Uses `.dark` class for manual toggle
2. **Media-based**: Respects system preference automatically
3. **Hybrid**: Manual toggle with system default
**Provider Setup:**
```typescript
// Copy theme provider template
cp ./skills/tailwind-shadcn-setup/templates/theme-provider.tsx components/theme-provider.tsx
```
**Theme Toggle Component:**
```bash
# Add theme toggle button
npx shadcn@latest add dropdown-menu
cp ./skills/tailwind-shadcn-setup/examples/theme-toggle.tsx components/theme-toggle.tsx
```
### 5. Adding Components
Install shadcn/ui components as needed:
```bash
# Add individual components
npx shadcn@latest add button
npx shadcn@latest add card
npx shadcn@latest add input
npx shadcn@latest add form
# Add multiple components at once
npx shadcn@latest add button card input form dialog sheet
```
**Common Component Sets:**
- **Forms**: button, input, label, select, textarea, checkbox, radio-group, form
- **Layout**: card, separator, aspect-ratio, scroll-area
- **Navigation**: navigation-menu, menubar, dropdown-menu, tabs
- **Feedback**: toast, alert, alert-dialog, dialog
- **Data**: table, data-table, pagination
### 6. Custom Component Configuration
Create custom components using shadcn/ui primitives:
```typescript
// Example: Custom button variant
import { Button } from "@/components/ui/button"
<Button variant="default">Default</Button>
<Button variant="destructive">Destructive</Button>
<Button variant="outline">Outline</Button>
<Button variant="secondary">Secondary</Button>
<Button variant="ghost">Ghost</Button>
<Button variant="link">Link</Button>
```
**Extending Components:**
```typescript
// Add custom variants in tailwind.config.ts
// Components automatically use CSS variables for theming
```
## Examples
### Example 1: Complete Setup for New Next.js Project
```bash
# 1. Install Tailwind CSS
bash ./skills/tailwind-shadcn-setup/scripts/install-tailwind.sh
# 2. Initialize shadcn/ui
bash ./skills/tailwind-shadcn-setup/scripts/init-shadcn.sh
# 3. Setup theme and dark mode
bash ./skills/tailwind-shadcn-setup/scripts/setup-dark-mode.sh
# 4. Add common components
npx shadcn@latest add button card input form dialog toast
# 5. Copy theme toggle component
cp ./skills/tailwind-shadcn-setup/examples/theme-toggle.tsx components/theme-toggle.tsx
```
**Result:** Fully configured Next.js project with Tailwind, shadcn/ui, dark mode, and essential components
### Example 2: Custom Theme with Brand Colors
```bash
# 1. Run theme setup
bash ./skills/tailwind-shadcn-setup/scripts/setup-theme.sh
# 2. Edit CSS variables for brand colors
# Modify app/globals.css to use your brand colors
# Example: Primary color = oklch(0.5 0.2 250) for brand blue
# 3. Test theme with sample components
cp ./skills/tailwind-shadcn-setup/examples/theme-showcase.tsx app/page.tsx
```
**Result:** Custom-branded design system using your colors while maintaining shadcn/ui components
### Example 3: Form-Heavy Application Setup
```bash
# 1. Complete base setup
bash ./skills/tailwind-shadcn-setup/scripts/install-tailwind.sh
bash ./skills/tailwind-shadcn-setup/scripts/init-shadcn.sh
# 2. Add all form-related components
npx shadcn@latest add form input label select textarea checkbox radio-group switch slider
# 3. Install react-hook-form and zod (form dependencies)
npm install react-hook-form zod @hookform/resolvers
# 4. Copy form example template
cp ./skills/tailwind-shadcn-setup/examples/sample-form.tsx components/forms/sample-form.tsx
```
**Result:** Complete form setup with validation, accessibility, and consistent styling
## Requirements
**Dependencies:**
- Next.js 13.4+ (App Router or Pages Router)
- React 18+
- Node.js 18.17+ or 20+
- TypeScript (recommended)
**Package Manager:**
- npm, pnpm, yarn, or bun (any modern package manager)
**Project Structure:**
- Next.js project initialized with `create-next-app`
- `app/` directory (App Router) or `pages/` directory (Pages Router)
- `components/` directory for UI components
- `lib/` directory for utilities
**For Dark Mode:**
- `next-themes` package (automatically installed by shadcn CLI)
- Client-side provider component
## Configuration Files Created
**tailwind.config.ts:**
```typescript
import type { Config } from "tailwindcss"
const config: Config = {
darkMode: ["class"],
content: [
"./pages/**/*.{ts,tsx}",
"./components/**/*.{ts,tsx}",
"./app/**/*.{ts,tsx}",
"./src/**/*.{ts,tsx}",
],
theme: {
extend: {
// CSS variable-based theming
},
},
plugins: [require("tailwindcss-animate")],
}
export default config
```
**components.json:**
```json
{
"$schema": "https://ui.shadcn.com/schema.json",
"style": "default",
"rsc": true,
"tsx": true,
"tailwind": {
"config": "tailwind.config.ts",
"css": "app/globals.css",
"baseColor": "slate",
"cssVariables": true
},
"aliases": {
"components": "@/components",
"utils": "@/lib/utils"
}
}
```
**app/globals.css:**
- `:root` variables for light mode
- `.dark` variables for dark mode
- Base layer imports
- Tailwind directives
## Best Practices
**CSS Variables Over Utility Classes:**
- Use `cssVariables: true` in components.json
- Allows runtime theme switching
- Better for multi-theme applications
- Easier to customize without recompiling
**Component Organization:**
```
components/
├── ui/ # shadcn/ui components (auto-generated)
│ ├── button.tsx
│ ├── card.tsx
│ └── inRelated 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.