agentleFS
toy-cranetoy-crane/claude-code-playbook-template/.agents/skills/shadcn/SKILL.md

shadcn

Skill77 starsChanged 6 days agoNo licenceView on GitHub

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

  • Installs packages

190 other projects use a version of this, 150 of them edited; 140 of 149 edited versions we compared changed its rules; 8 new projects in the last 4 weeks, against 23 the 4 before.

How people change it

140 of 149 edited versions changed its rules, and some changes recur.

Of the 149 edited versions we compared: 9 keep every rule, 140 made changes of their own.

Rules people drop

  1. When the user asks for a design system from a DESIGN.md (or a brand spec), with or without a preset, follow [design-system.md](./design-system.md) end to end:dropped by 139 of 140
  2. Read the DESIGN.md frontmatter, Do's and Don'ts, and Known Gaps before editing.dropped by 139 of 140
  3. Verify in a browser: typecheck, no console errors, loads at the top, no horizontal overflow, dark mode.dropped by 139 of 140
  4. Toast follows the project base. Use toast from the toast component for Base UI projects. Use toast() from sonner for Radix and React Aria projects.dropped by 89 of 140
  5. Never decode preset codes or build preset URLs manually. Use npx shadcn@latest preset decode <code>, preset url <code>, or preset open <code>. For project-aware preset detection, use npx shadcn@latest preset resolve.dropped by 47 of 140
  6. Apply preset codes directly with the CLI. Use npx shadcn@latest apply <code> for existing projects, or npx shadcn@latest init --preset <code> when initializing.dropped by 47 of 140
  7. No local changes → safe to overwrite.dropped by 2 of 140
  8. When the user asks to update a component from upstream while keeping their local changes, use --dry-run and --diff to intelligently merge. NEVER fetch raw files from GitHub manually — always use the CLI.dropped by 1 of 140

Rules people add

  1. Toast via sonner. Use toast() from sonner.added by 87 of 140
  2. A rule we can't quote: its licence doesn't allow itadded by 24 of 140
  3. Use when adding new components from shadcn/ui or community registries.added by 3 of 140
  4. Use when styling, composing, or debugging existing shadcn/ui components.added by 3 of 140
  5. Use when initializing a new project or switching design system presets.added by 3 of 140
  6. Use to retrieve component documentation, examples, and API references.added by 3 of 140

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 8 new projects took it in the last 4 weeks, 0.3× the 4 weeks before.

Week of Sep 20: 2 new projectsWeek of Sep 27: 5 new projectsWeek of Oct 4: 11 new projectsWeek of Oct 11: 5 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 1 new projectWeek of Nov 1: 7 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

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-uiSkill

    migrate-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-itSkill

    nuqs

    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

  • bergsideSkill

    friendly

    Approachable, intuitive design with rounded elements, ample whitespace, and soft pastel color palettes.

    Also in 4 projects that use this

  • bergsideSkill

    professional

    Polished, business-ready design with modern typography, structured layouts, and a trustworthy visual identity.

    Also in 4 projects that use this

  • SupabaseSkill

    react-hook-form

    Correct React Hook Form usage anywhere in the monorepo — data flow, subscriptions,

    Also in 5 projects that use this

  • barisariburnuSkill

    tanstack

    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

The file

Show its rules and text

We split this skill into the rules it gives an agent

23 rules. 1 is common, 2 are distinctive, and 20 are very specific to this project.

  • 1

    Common

    Most of the 174 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 20

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 174 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.