What problem does it solve? Building UI with shadcn/ui requires knowing the correct component composition, CLI commands, preset handling, and styling conventions; mistakes like wrong imports, missing accessibility titles, or raw color values lead to inconsistent and broken interfaces. ## Core Features & Use Cases - Component Management: Search registries, add components, preview changes with dry-run and diff, and smart-merge upstream updates while preserving local modifications. - Preset & Project Workflows: Initialize projects with templates and presets, apply or switch preset codes, and read project context (aliases, Tailwind version, icon library, base vs radix) via the CLI. - Enforced UI Rules: Apply critical rules for forms, composition, icons, styling, and chat interfaces, including FieldGroup layouts, data-icon attributes, semantic color tokens, and MessageScroller-based chat UI. - Use Case: When asked to build a settings form in a Next.js shadcn project, the Skill checks installed components, fetches component docs, and generates code using FieldGroup, ToggleGroup, and proper validation states. ## Quick Start Ask the agent to add a shadcn component or build a UI pattern, for example: add a dialog and card to my project and build a profile settings form with validation states.