What problem does it solve? Working with shadcn/ui requires knowing the correct CLI commands, component composition rules, and styling conventions; this Skill provides project-aware context and enforced rules so generated UI code follows shadcn/ui best practices instead of reinventing markup. ## Core Features & Use Cases - CLI-driven component management: Add, search, view, diff, and update components from official, namespaced, or GitHub registries using the project's own package runner. - Enforced composition and styling rules: Critical rules for forms (FieldGroup/Field), icons (data-icon), semantic colors, gap-based spacing, and base-vs-radix API differences with Incorrect/Correct code pairs. - Preset and theme workflows: Initialize projects with named presets or preset codes, apply or merge presets into existing projects, and customize themes via CSS variables. - Use Case: When asked to build a settings form in a Next.js project with a components.json file, the Skill reads project context via npx shadcn@latest info, fetches component docs, and generates code using FieldGroup, ToggleGroup, and semantic tokens. ## Quick Start Ask the agent to add a shadcn/ui component such as a dialog or build a settings form in a project that contains a components.json file.