shadcn
Skill194 starsChanged 47 days agoMITView on GitHub
Use when adding, updating, composing, or debugging source components managed by shadcn; changing apps/desktop/components.json, registries, or presets; or running the shadcn CLI. Do not use for cosmetic layout or styling changes that only add classes around existing primitives.
189 other projects use a version of this.
Adopted by
Most recently taken up by
- shashidharbabu/rocketride-design-skillstheir own version, first seen Nov 15, 2026
- udaykumar-dhokia/mcp-flowtheir own version, first seen Nov 15, 2026
- theishandubey/dotclaudetheir own version, first seen Nov 15, 2026
- debugbundle/debugbundletheir own version, first seen Nov 15, 2026
- Fractera/web4-node-starter-kittheir own version, first seen Nov 15, 2026
- moi-computer/moitheir own version, first seen Nov 15, 2026
Used with
Projects with it also use migrate-radix-to-base, nuqs and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
shadcn-uiSkillmigrate-radix-to-base
Migrates React projects and components from Radix UI to Base UI. Use when asked to migrate from radix, move to base-ui, convert radix primitives, or switch a shadcn project's base library. Handles single components ("migrate accordion") and whole projects.
Also in 15 projects that use this
thongdn-itSkillnuqs
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.
Also in 4 projects that use this
bergsideSkillfriendly
Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.
Also in 4 projects that use this
bergsideSkillprofessional
Polished, business-ready design with modern typography, structured layouts, and a trustworthy visual identity.
Also in 4 projects that use this
SupabaseSkillreact-hook-form
Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,
Also in 5 projects that use this
barisariburnuSkilltanstack
Expert assistance for TanStack Router, Query (v5), and Table (v8). Use when users need help with file-based routing, type-safe navigation, data loading, search params, queries, mutations, optimistic updates, infinite queries, table state management, or debugging TanStack libraries.
Also in 4 projects that use this
- +5 more from bergside
Other versions189 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 189
- shadcn-ui/ui★ 128ksame name
- coollabsio/coolify★ 66ksame name
- kriasoft/react-starter-kit★ 24ksame name
- MODSetter/SurfSense★ 17ksame name
- udecode/plate★ 17ksame name
- spree/spree★ 16ksame name
- trycompai/crm★ 12ksame name
- 1weiho/open-slide★ 9.7ksame name
- open-slide/open-slide★ 9.7ksame name
- openai/plugins★ 7.8ksame name
179 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- diffsSkill
- opencode-coverageSkill
- opencode-runtimeSkill
- palot-designSkill
- palot-desktop-devSkill
- palot-performanceSkill
- test-palot-desktopSkill
- treesSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Do not use npx, pnpm dlx, bunx, or an @latest CLI.
- Distinctive: line 29
Use the CLI rather than fetching upstream source manually:
- Very specific: line 31
Run vp exec -- shadcn add <component> --dry-run to list affected files.
- Very specific: line 32
Run vp exec -- shadcn add <component> --diff <file> for each customized file.
- Very specific: line 34
Use --overwrite only when the user explicitly authorizes replacing local changes.
- Distinctive: line 38
Use semantic theme tokens rather than raw colors or manual dark-mode overrides.
- Very specific: line 39
Use gap-*, size-*, truncate, and cn() rather than equivalent verbose utilities.
- Very specific: line 42
Prefer shared components such as Alert, Empty, Separator, Skeleton, and Badge over hand-built equivalents.
- Distinctive: line 43
Keep layout decisions in call sites and reusable visual behavior in component variants.
- Distinctive: line 47
Read only the branch needed for the task:
“Common” is measured: kept by at least 6 in 10 of the 186 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
shadcn/ui in Palot
Palot pins the shadcn CLI in apps/desktop. Run it from that workspace through Vite+:
vp exec -- shadcn info --json
vp exec -- shadcn docs <component>Do not use npx, pnpm dlx, bunx, or an @latest CLI. Preserve the repository pin and the aliases, Tailwind file, primitive base, icon library, and registries reported by info.
Choose the work
- Existing-source fixes: inspect the component and relevant callers first. Use the local implementation as the contract; CLI discovery and external docs are unnecessary when that evidence answers the question.
- Adding components or changing registry/configuration: read repository-root
../../../apps/desktop/components.jsonand runvp exec -- shadcn info --jsonfromapps/desktop. Prefer existing local primitives and variants; usesearchorviewwhen looking for a missing component. - Unclear APIs or upstream behavior: use
vp exec -- shadcn docs <component>and fetch the relevant returned documentation. Reconcile it with the local source before applying it to customized components. - Upstream component updates: follow the preview workflow below.
Inspect changed imports and CSS where applicable, then follow the formatting and validation workflow in the development guide. Shadcn CLI edits bypass OpenCode's native formatter hook, so format those files explicitly while respecting the repository's exclusions.
Updating components
Use the CLI rather than fetching upstream source manually:
- Run
vp exec -- shadcn add <component> --dry-runto list affected files. - Run
vp exec -- shadcn add <component> --diff <file>for each customized file. - Apply upstream changes while preserving local behavior and imports.
- Use
--overwriteonly when the user explicitly authorizes replacing local changes.
Project rules
- Use semantic theme tokens rather than raw colors or manual dark-mode overrides.
- Use
gap-*,size-*,truncate, andcn()rather than equivalent verbose utilities. - Compose forms with
FieldGroupandField; put collection items inside their matching group. - Dialog-like surfaces require an accessible title.
- Prefer shared components such as
Alert,Empty,Separator,Skeleton, andBadgeover hand-built equivalents. - Keep layout decisions in call sites and reusable visual behavior in component variants.
References
Read only the branch needed for the task:
- Styling and Tailwind:
rules/styling.md - Forms and validation:
rules/forms.md - Component composition:
rules/composition.md - Base UI versus Radix APIs:
rules/base-vs-radix.md - Icons:
rules/icons.md - Chat primitives:
rules/chat.md - CLI commands:
cli.md - Registries:
registry.md - Presets and customization:
customization.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

