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, so generated UI code compiles and follows accessibility and styling conventions on the first try. ## Core Features & Use Cases - CLI-driven component management: init projects with presets, add/search/view components from registries, preview changes with --dry-run and --diff, and smart-merge upstream updates without losing local customizations. - Enforced composition and styling rules: FieldGroup-based forms, group-wrapped menu items, semantic color tokens, data-icon attributes, and base-vs-radix API differences, each backed by Incorrect/Correct code pairs. - Preset and theme workflows: apply named presets or preset codes, switch themes with overwrite/partial/merge/skip strategies, and customize CSS variables in the project's Tailwind config. - Use Case: A developer asks to build a settings form in a Next.js project. The Skill reads the project context, confirms installed components, fetches docs for Field and ToggleGroup, and generates code using the project's actual aliases and icon library. ## Quick Start Ask the assistant to add a shadcn/ui component such as a dialog or build a form, and it will run the shadcn CLI and generate compliant code.