What problem does it solve? Building UI with shadcn/ui requires knowing dozens of composition rules, CLI commands, preset workflows, and base-vs-radix API differences. This Skill injects project context and enforces correct component usage so generated code follows shadcn/ui conventions instead of hand-rolled markup. ## Core Features & Use Cases - Component Management: Search registries, add components, preview changes with --dry-run/--diff, and smart-merge upstream updates while preserving local modifications. - Preset & Theme Workflows: Initialize projects with named presets or preset codes, apply or switch presets with overwrite, partial, merge, or skip strategies. - Enforced UI Rules: Critical rules for forms (FieldGroup/Field), composition (Groups, Dialog titles, Card structure), icons (data-icon), styling (semantic tokens, gap-* spacing), and chat primitives (MessageScroller, Bubble, Attachment, Marker). - Use Case: Ask for a settings form with validation, and get code using FieldGroup, Field, data-invalid/aria-invalid states, and semantic color tokens matched to your project's base, icon library, and Tailwind version. ## Quick Start Ask the assistant to add a shadcn/ui dialog component to the project and build a profile editing form inside it.