shadcn
Teaches Claude to add and compose shadcn/ui components through the CLI rather than inventing one-off widgets that fight your design system.
What it is for
Many 2026 React codebases ship UI through shadcn/ui. This skill aligns Claude with that workflow so you get composed components—Dialog, Sheet, Form patterns via the CLI—instead of novel CSS islands that fight your design system and break accessibility norms your team already standardized.
Rank #8, score 85/100 (Nov 21, 2026). ~424K install reads as context. It sits below taste and performance skills because it is stack-specific: high value inside shadcn shops, low value elsewhere.
Why this score
Eighty-five reflects a clear, practical job and a well-known publisher, tempered by lock-in. On an editorial shortlist that also ranks methodology and document skills, a component-system helper should not outrank broader jobs. Inside a shadcn/ui repo, though, it often beats generic “make a nice form” prompting.
Who should install
Yes if your repo already uses (or is deliberately adopting) shadcn/ui. No if you have a different component library—Claude will fight your stack and suggest the wrong primitives.
Install vs skip examples
- Install: You need a settings sheet built from existing shadcn primitives.
- Install: Claude keeps freehanding buttons that ignore your
components/uiconventions. - Skip: Material UI / Chakra / custom system only—do not install shadcn “just in case.”
- Skip: You only need a first-viewport taste pass with no component work—use frontend-design.
What SKILL.md typically covers
Expect CLI-oriented instructions for adding components and composing patterns. Confirm paths match your project’s shadcn setup (aliases, components.json, package manager). Read the installed file; upstream CLI flags change.
Install
npx skills add shadcn/ui --skill shadcn
Verify owner shadcn/ui before you paste. Install guide · Safety checklist.
How to use it well
- Tell Claude which surface you are building and which primitives you already have.
- Prefer “add via CLI, then compose” over “invent a new Button.”
- Keep brand and layout constraints in the prompt or
CLAUDE.mdso composition does not drift into generic AI chrome. - Pair with frontend-design when the page still looks template-y after components land.
Common mistakes: installing the skill in a non-shadcn repo; letting Claude add twenty components you will never use; mixing shadcn advice with a second UI kit skill in the same session.
vs nearby
- frontend-design — overall taste vs component system plumbing. Complementary when prompts name the active job.
- vercel-react-best-practices — performance vs UI composition. Sequence matters: compose, then profile.
- Superpowers — coding process vs UI kit workflow.
- pdf / xlsx — document deliverables, not screen components.
Risks and caveats
Wrong-repo installs and mismatched shadcn versions. Verify owner shadcn/ui. The skill can encourage adding components you do not need—keep PRs small. It does not replace accessibility review or design QA.
Source and date
Publisher shadcn, skill shadcn, Nov 21, 2026.
Hub: Claude skills for design. Ranking: best Claude skills. Related: frontend-design review, Claude Code skills.
FAQ
What does the shadcn skill do?
It steers Claude to use the shadcn/ui workflow—adding and composing components via the CLI—instead of freehanding custom widgets.
How do I install the shadcn skill?
npx skills add shadcn/ui --skill shadcn
Should I install shadcn and frontend-design together?
Often yes: frontend-design for page taste, shadcn for component plumbing. Keep prompts clear about which job you want in the moment.
What if my repo is not on shadcn/ui?
Skip this skill. Claude will drag you toward the wrong stack; use your real component system docs instead.