What problem does it solve? Building consistent UI with shadcn/ui requires knowing the correct component APIs, composition patterns, Tailwind conventions, and CLI workflows. This Skill provides project-aware context, enforced styling rules, and CLI guidance so generated code matches the project's actual configuration instead of generic guesses. ## Core Features & Use Cases - Component management via CLI: Search registries, add components, preview changes with --dry-run/--diff, and smart-merge upstream updates while preserving local modifications. - Enforced code conventions: Critical rules for forms (FieldGroup/Field), styling (semantic tokens, gap-, size-), icons (data-icon), and composition (Groups, Titles, AvatarFallback) with Incorrect/Correct examples. - Project-aware generation: Reads framework, aliases, Tailwind version, base (radix vs base), and icon library from npx shadcn@latest info so imports and APIs match the project. - Use Case: Ask for a settings form and get code using FieldGroup, ToggleGroup, data-invalid validation, semantic colors, and the project's configured icon library — then install missing components with the correct package runner. ## Quick Start Ask the assistant to add a shadcn/ui component or build a UI pattern, for example: create a dashboard with stat cards using shadcn/ui and install any missing components.