shadcn-code-review — Claude Code skill: what it does, how to install
shadcn-code-review audits React components built with shadcn/ui, Radix primitives, and Tailwind CSS. Catches CVA mistakes, broken asChild slots, and missing accessibility states.
Apache-2.0 206 installs ★ 89 updated 2026-09-15
npx skills add existential-birds/beagle --skill shadcn-code-review -a claude-codeWhat shadcn-code-review does
This skill defines structured checks for shadcn/ui codebases. It verifies that cn() handles class names rather than raw CVA variants, checks whether VariantProps is exported, and ensures asChild composition imports @radix-ui/react-slot. It also tracks data-slot attributes and state-based styling using has() selectors.
Hard review gates block speculative feedback before reporting. Without an exact quote or line range, the finding fails the initial review gate. The model cannot guess issues from git diffs alone.
Untouched library internals pass without warnings. The skill accepts Tailwind v4 CSS variable formats like max-h-(--var) and arbitrary values without raising flags. Custom modifications and application state integrations remain the primary focus of the review.
What it helps with
- verify proper separation of CVA variants from className props
- catch missing focus-visible and aria-invalid form states
- validate asChild composition with Radix Slot primitives
- add data-slot attributes to multipart component structures
Example prompts for the agent
- Review Button.tsx against the shadcn-code-review checklist
- Check this custom dialog component for missing focus-visible and aria states
- Verify that Card.tsx uses data-slot attributes and proper CVA exports
How to install shadcn-code-review
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill shadcn-code-review -a claude-code2Manually: put the files in place
~/.claude/skills/shadcn-code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/shadcn-code-review/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill shadcn-code-review -a codex2Manually: put the files in place
.agents/skills/shadcn-code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill shadcn-code-review -a cursor2Manually: put the files in place
.cursor/skills/shadcn-code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install existential-birds/beagle plugins/beagle-react/skills/shadcn-code-review2Manually: put the files in place
.github/skills/shadcn-code-review/SKILL.md1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill shadcn-code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/existential-birds/beagle --path plugins/beagle-react/skills/shadcn-code-reviewManually: put the files in place
.devin/skills/shadcn-code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill shadcn-code-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about shadcn-code-review
How do I install shadcn-code-review in Claude Code?
Run npx skills add existential-birds/beagle --skill shadcn-code-review -a claude-code in your terminal.
Does shadcn-code-review flag standard copied shadcn code?
No. The skill treats copied library internals and default Radix behaviors as valid, focusing solely on custom modifications and missing integration code.
What Tailwind syntax is explicitly allowed during review?
Tailwind v4 CSS variable formats like max-h-(--var) and arbitrary values like text-[color:var(--x)] pass checks without warnings.
Source text
SKILL.md · Apache-2.0
--- name: shadcn-code-review description: Reviews shadcn/ui components for CVA patterns, composition with asChild, accessibility states, and data-slot usage. Use when reviewing React components using shadcn/ui, Radix primitives, or Tailwind styling. --- # shadcn/ui Code Review ## Quick Reference | Issue Type | Reference | |------------|-----------| | className in CVA, missing VariantProps, compound variants | [references/cva-patterns.md](references/cva-patterns.md) | | asChild without Slot, missing Context, component composition | [references/composition.md](references/composition.md) | | Missing focus-visible, aria-invalid, disabled states | [references/accessibility.md](references/accessibility.md) | | Missing data-slot, incorrect CSS targeting | [references/data-slot.md](references/data-slot.md) | ## Review Checklist - [ ] `cn()` receives className, not CVA variants - [ ] `VariantProps<typeof variants>` exported for consumers - [ ] Compound variants used for complex state combinations - [ ] `asChild` pattern uses `@radix-ui/react-slot` - [ ] Context used for component composition (Card, Accordion, etc.) - [ ] `focus-visible:` states, not just `:focus` - [ ] `aria-invalid`, `aria-disabled` for form states - [ ] `disabled:` variants for all interactive elements - [ ] `sr-only` for screen reader text - [ ] `data-slot` attributes for targetable composition parts - [ ] CSS uses `has()` selectors for state-based styling - [ ] No direct className overrides of variant styles ## Hard gates (before writing findings) Run these in order. **Do not draft user-facing findings until every gate passes** for the batch you are about to report. 1. **Location evidence** — **Pass:** Each issue lists a repo path and either a line range or a short verbatim quote from the file you read (not from memory or diff-only guesswork). 2. **Exemption check** — **Pass:** For each issue, you can state in one line why it is *not* covered by [Valid Patterns (Do NOT Flag)](#valid-patterns-do-not-flag). 3. **Context-sensitive claims** — **Pass:** For accessibility or Radix-related flags, you checked the file for imports/wrappers showing what actually runs (or you cite the concrete gap). 4. **Protocol** — **Pass:** You completed the Pre-Report Verification Checklist in [review-verification-protocol](../review-verification-protocol/SKILL.md) for this review. ## Valid Patterns (Do NOT Flag) These are correct patterns that should NOT be flagged as issues: - `max-h-(--var)` - correct Tailwind v4 CSS variable syntax (NOT v3 bracket notation) - `text-[color:var(--x)]` - valid arbitrary value syntax - Copying shadcn component code into project - intended usage pattern - Not documenting copied shadcn components - library internals, not custom code - Using cn() with many arguments - composition is the pattern - Conditional classes in cn() arrays - valid Tailwind pattern - Extending primitive components without additional docs - well-known base ## Context-Sensitive Rules Apply these rules with appropriate context awareness: - Flag accessibility issues ONLY IF not handled by Radix primitives underneath - Flag missing aria labels ONLY IF component isn't using accessible radix primitive - Flag variant proliferation ONLY IF variants could be composed from existing - Flag component documentation ONLY IF it's custom code, not copied shadcn ## Library Convention Note shadcn/ui components are designed to be copied and modified. Code review should focus on: - Custom modifications made to copied components - Integration with application state/data - Accessibility in custom usage contexts Do NOT flag: - Standard shadcn component internals - Radix primitive usage patterns - Default variant implementations ## When to Load References - Reviewing variant definitions → cva-patterns.md - Reviewing component composition with asChild → composition.md - Reviewing form components or interactive elements → accessibility.md - Reviewing multi-part components (Card, Select, etc.) → data-slot.md ## Review Questions 1. Are CVA variants properly separated from className props? 2. Does asChild composition work correctly with Slot? 3. Are all accessibility states (focus, invalid, disabled) handled? 4. Are data-slot attributes used for component part targeting? 5. Can consumers extend variants without breaking composition? ## Before Submitting Findings Complete [Hard gates](#hard-gates-before-writing-findings) (especially gate 4), then report only issues that still pass the [review-verification-protocol](../review-verification-protocol/SKILL.md) pre-report checks.
© existential-birds · Apache-2.0 · existential-birds/beagle