What problem does it solve? Working with shadcn/ui requires knowing the correct CLI commands, component composition rules, and project-specific configuration (aliases, Tailwind version, icon library, base vs radix primitives). This Skill eliminates guesswork by injecting live project context and enforcing correct usage patterns when adding, updating, debugging, or composing components. ## Core Features & Use Cases - CLI-driven component management: Search registries, add components, preview changes with --dry-run/--diff, and smart-merge upstream updates while preserving local modifications. - Enforced composition and styling rules: Critical rules for forms (FieldGroup/Field), styling (semantic tokens, gap-* spacing), icons (data-icon), and component structure (Groups, Titles, AvatarFallback) with Incorrect/Correct code pairs. - Preset and theme workflows: Initialize projects with named presets or preset codes, switch presets via reinstall/merge/skip strategies, and customize themes through CSS variables. - Use Case: A developer asks to build a settings form in a Next.js project. The Skill reads the project context, fetches component docs via the CLI, and generates code using FieldGroup, ToggleGroup, and proper validation attributes matching the project's base (radix vs base) and icon library. ## Quick Start Ask the assistant to add a shadcn/ui component such as a dialog or build a settings form using shadcn/ui in your project.