What problem does it solve?
This skill keeps shadcn/ui components consistent by collecting project context, enforcing styling and composition rules, and guiding CLI commands so teams do not ship misaligned layouts or theme variables.
Core Features & Use Cases
- Documents CLI usage patterns for init, add, search, docs, info, and diff commands with the correct package runner while highlighting registries, preset switching, and recommended workflows.
- Highlights styling, forms, composition, icons, and base-vs-radix rules so component additions always use semantic tokens, FieldGroup structures, proper groups, and accessible overlays.
- Provides project-specific context such as aliases, resolved paths, global CSS entry points, monorepo layout, update strategies, registry handling, and complements additional skills for template placement, design direction, and Tailwind practices.
Quick Start
Start by asking for the shadcn info and docs outputs via the correct package runner so you can inspect aliases, Tailwind settings, registries, and installed components before making any changes.