What problem does it solve? Working with shadcn/ui involves many project-specific details — the base library (radix vs base), Tailwind version, icon library, aliases, and presets — and getting component composition, styling, or CLI usage wrong leads to broken, inconsistent UI. This Skill injects the live project context and enforces correct patterns for adding, updating, styling, and composing shadcn/ui components. ## Core Features & Use Cases - Component lifecycle management: Search registries, preview changes with --dry-run/--diff, add components, and smart-merge upstream updates while preserving local modifications. - Enforced UI rules: Critical Incorrect/Correct rules for forms (FieldGroup/Field), composition (Groups, Dialog titles, Card structure), icons (data-icon), styling (semantic tokens, gap-*, cn()), and chat UI (MessageScroller, Bubble, Attachment, Marker). - Preset and registry workflows: Initialize projects with named presets or preset codes, switch presets via overwrite/partial/merge/skip strategies, and author or consume custom and GitHub registries. - Use Case: Ask to build a settings form in a Next.js shadcn project, and the Skill produces code using FieldGroup, ToggleGroup, data-invalid validation, semantic colors, and the project's configured icon library. ## Quick Start Ask the assistant to add a shadcn/ui component or build a UI pattern in your project, for example: add a login form block to my shadcn project using the correct registry and project conventions.