react-shadcn
shadcn/ui for React with TanStack Form. Use when building UI components, forms, dialogs, tables, toasts, or accessible components.
What this skill does
# shadcn/ui for React Beautiful, accessible components built on Radix UI with Tailwind CSS styling. ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze existing components and patterns 2. **fuse-ai-pilot:research-expert** - Verify latest shadcn/ui docs via Context7/Exa 3. **mcp__shadcn__*** - Search registry for component availability After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Building UI components for React applications (Vite, CRA) - Need accessible, customizable form components (inputs, selects, checkboxes) - Implementing dialogs, sheets, drawers, or overlay patterns - Creating data tables with sorting, filtering, and pagination - Building navigation menus, sidebars, or command palettes - Need toast notifications or alert feedback components ### Why shadcn/ui | Feature | Benefit | |---------|---------| | Copy/paste model | Components copied to your project, full ownership | | Radix UI foundation | Accessibility built-in, unstyled primitives | | Tailwind CSS styling | Utility-first, easy customization | | TanStack Form ready | Modern form library with Field pattern | | Lucide icons | Consistent, customizable icon set | --- ## Critical Rules 1. **NEVER create components manually** - Always install with `bunx --bun shadcn@latest add` 2. **TanStack Form only** - NOT React Hook Form for all form implementations 3. **Radix UI primitives** - Components built on Radix (NOT Base UI) 4. **Lucide icons** - Default icon library, NOT Remix icons or others 5. **Field pattern** - Use Field, FieldLabel, FieldError for form fields 6. **SOLID paths** - Components at `@/modules/cores/shadcn/components/ui/` --- ## Architecture ### Component Foundation - **Radix UI** - Headless, accessible primitives (Dialog, Select, Popover, Tabs) - **Tailwind CSS v4** - Styling via utility classes, CSS-first config - **class-variance-authority** - Variant management for component styles - **clsx + tailwind-merge** - Conditional class composition via `cn()` utility ### Project Structure Components installed to `@/modules/cores/shadcn/components/ui/` following SOLID architecture. Utils at `@/modules/cores/lib/utils.ts` with `cn()` helper function. --- ## MCP Server Integration Create `.mcp.json` at project root for Claude Code integration with shadcn registry. ### Available MCP Tools - `mcp__shadcn__search_items_in_registries` - Search available components - `mcp__shadcn__view_items_in_registries` - View component source code - `mcp__shadcn__get_item_examples_from_registries` - Get usage examples - `mcp__shadcn__get_add_command_for_items` - Get installation commands See [installation.md](references/installation.md) for complete MCP setup. --- ## Component Categories | Category | Components | Primary Reference | |----------|------------|-------------------| | Setup | Init, configuration, theming, icons | [installation.md](references/installation.md) | | Forms | Button, Input, Field, Select, Checkbox, Switch, Slider | [field-patterns.md](references/field-patterns.md) | | Overlay | Dialog, Sheet, Drawer, Popover, Tooltip, HoverCard | [dialog.md](references/dialog.md) | | Feedback | Alert, Toast (Sonner), Progress, Skeleton, Spinner | [toast.md](references/toast.md) | | Data Display | Table, Badge, Avatar, Calendar, Chart, Carousel | [table.md](references/table.md) | | Navigation | Breadcrumb, DropdownMenu, Command, Sidebar, Tabs | [sidebar.md](references/sidebar.md) | | Layout | Card, Accordion, Separator, ScrollArea, Resizable | [card.md](references/card.md) | --- ## Best Practices 1. **Field components** - Use new Field pattern for consistent form field structure 2. **Client Components** - React apps are client-side by default 3. **Sonner for toasts** - Modern toast notifications over legacy toast 4. **MCP tools first** - Use `mcp__shadcn__*` to explore before implementing 5. **Theming via CSS variables** - Customize colors in `index.css` `:root` 6. **Accessibility** - Rely on Radix UI keyboard navigation and ARIA --- ## Reference Guide | Need | Reference | |------|-----------| | Initial setup | [installation.md](references/installation.md), [configuration.md](references/configuration.md) | | Form patterns | [field-patterns.md](references/field-patterns.md), [form-examples.md](references/form-examples.md) | | Theme customization | [theming.md](references/theming.md) | | Data tables | [table.md](references/table.md) | | Modal dialogs | [dialog.md](references/dialog.md), [alert-dialog.md](references/alert-dialog.md) | | Navigation | [sidebar.md](references/sidebar.md), [navigation-menu.md](references/navigation-menu.md) |
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.