agentleFS
Sign inStart free
EstebanT1112EstebanT1112/codex-engineering-workflow/skills/shadcn/SKILL.md

shadcn

Skill0 starsChanged 2 months agoMITView on GitHub

Build, add, compose, or repair shadcn/ui components in a repository that already uses shadcn or when the user explicitly requests it. Use repository configuration and installed versions; do not activate for unrelated Tailwind or generic React work.

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

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the local component and its dependencies before adding or changing anything.

    line 14
  2. Distinctive:

    Use the repository's package manager and pinned versions.

    line 15
  3. Distinctive:

    When adding a component, inspect the generated diff and keep only files required by the requested behavior.

    line 17
  4. Distinctive:

    Test interaction and state behavior, then run relevant typecheck, lint, build, and browser checks.

    line 18
  5. Very specific:

    Never run an @latest installer or add a registry without explicit need and review.

    line 22
  6. Distinctive:

    Do not replace locally customized components merely to match upstream output.

    line 24
  7. Very specific:

    Use frontend-design for visual direction and frontend-ui-engineering for the surrounding product flow.

    line 25

“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 Repository Work

Workflow

  1. Confirm shadcn from repository evidence such as components.json, component paths, aliases, styling setup, and package manifests.
  2. Read the local component and its dependencies before adding or changing anything.
  3. Use the repository's package manager and pinned versions. Prefer existing primitives and variants.
  4. Preserve local tokens, composition patterns, accessibility behavior, server/client boundaries, and import aliases.
  5. When adding a component, inspect the generated diff and keep only files required by the requested behavior.
  6. Test interaction and state behavior, then run relevant typecheck, lint, build, and browser checks.

Boundaries

  • Never run an @latest installer or add a registry without explicit need and review.
  • A skill instruction does not authorize package installation, network access, overwrite, or deletion.
  • Do not replace locally customized components merely to match upstream output.
  • Use frontend-design for visual direction and frontend-ui-engineering for the surrounding product flow.

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.

Check your setup, free