What problem does it solve?
Provides a disciplined, CLI-driven workflow for adding, updating, fixing, and composing shadcn/ui components so teams avoid broken imports, inconsistent styling, and unsafe overwrites when integrating third-party registry components or switching presets.
Core Features & Use Cases
- Project-aware CLI integration: Uses the shadcn CLI via the project's package runner to inspect components.json, resolved paths, aliases, and Tailwind configuration before making changes.
- Safe install and update workflows: Supports dry-run, diff, and smart merge steps to preview changes, review diffs per-file, and preserve local modifications when updating upstream components.
- Composition, styling, and accessibility rules: Enforces composition patterns (groups, overlays, titles), styling best practices (semantic tokens, gap-* spacing, cn() usage), and icon import conventions to ensure consistent UI and accessibility.
- Preset and registry management: Guides switching or initializing presets (reinstall, merge, skip), requires explicit registry selection when adding components, and includes MCP tools for registry queries and audits.
Quick Start
Run the project's shadcn CLI with the package runner to inspect the project (info) and list or fetch docs for components before adding or updating them.