What problem does it solve?
shadcn/ui integration often stalls developers because the steps span discovery, dependency setup, config alignment (Tailwind and components.json), and accessibility-safe customization across many components.
Core Features & Use Cases
- Component discovery via MCP: Lists and retrieves shadcn/ui components/blocks, including metadata and demos, so you can choose the right pieces before installing.
- Deterministic setup workflow: Validates or initializes
components.json, checks Tailwind configuration expectations, and ensures import paths/aliases align with your project.
- Safe installation and customization: Guides direct CLI installs or manual integration, supports theme-level changes (CSS variables) and variant-level customization (cva), and emphasizes accessibility and TypeScript correctness.
- Common UI use cases: Accelerates building authentication layouts, sortable/filterable data tables, dashboards with navigation, and form flows with validation.
Quick Start
Ask: "Set up shadcn/ui in my Next.js + Tailwind project, verify components.json and path aliases, then add a button, card, tabs, and dialog with a brief checklist of best practices."