agentleFS
ItsWendellItsWendell/palot/.agents/skills/shadcn/SKILL.md

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

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

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
  1. Very specific:

    Do not use npx, pnpm dlx, bunx, or an @latest CLI.

    line 16
  2. Distinctive:

    Use the CLI rather than fetching upstream source manually:

    line 29
  3. Very specific:

    Run vp exec -- shadcn add <component> --dry-run to list affected files.

    line 31
  4. Very specific:

    Run vp exec -- shadcn add <component> --diff <file> for each customized file.

    line 32
  5. Very specific:

    Use --overwrite only when the user explicitly authorizes replacing local changes.

    line 34
  6. Distinctive:

    Use semantic theme tokens rather than raw colors or manual dark-mode overrides.

    line 38
  7. Very specific:

    Use gap-*, size-*, truncate, and cn() rather than equivalent verbose utilities.

    line 39
  8. Very specific:

    Prefer shared components such as Alert, Empty, Separator, Skeleton, and Badge over hand-built equivalents.

    line 42
  9. Distinctive:

    Keep layout decisions in call sites and reusable visual behavior in component variants.

    line 43
  10. Distinctive:

    Read only the branch needed for the task:

    line 47

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.json and run vp exec -- shadcn info --json from apps/desktop. Prefer existing local primitives and variants; use search or view when 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:

  1. Run vp exec -- shadcn add <component> --dry-run to list affected files.
  2. Run vp exec -- shadcn add <component> --diff <file> for each customized file.
  3. Apply upstream changes while preserving local behavior and imports.
  4. Use --overwrite only 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, and cn() rather than equivalent verbose utilities.
  • Compose forms with FieldGroup and Field; put collection items inside their matching group.
  • Dialog-like surfaces require an accessible title.
  • Prefer shared components such as Alert, Empty, Separator, Skeleton, and Badge over 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

Download now (ZIP)

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.