agentleFS
Sign inStart free
BuilderIOBuilderIO/agent-native/.agents/skills/shadcn-ui/SKILL.md

shadcn-ui

Skill7.6k starsChanged 5 months agoMITView on GitHub

Using the app's local UI adapter and Toolkit or shadcn primitives. Use when choosing or composing standard controls, implementing dialogs, menus, or forms, or changing component variants and theme tokens.

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 36 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the components already provided by the app.

    line 12
  2. Very specific:

    Use the app's configured design system and provider mapping for controls passed to shared Toolkit surfaces.

    line 25
  3. Distinctive:

    Prefer a primitive's built-in variant and size.

    line 33
  4. Very specific:

    Use the app's semantic theme tokens for reusable UI, such as bg-background, text-muted-foreground, border-border, and bg-primary.

    line 35
  5. Distinctive:

    Keep theme values in the app's existing CSS theme file.

    line 37
  6. Very specific:

    Use the control that matches the choice: Switch for a binary setting, Checkbox for independent multi-select, RadioGroup for one choice from …

    line 38
  7. Distinctive:

    Put selectable items inside their menu or list group primitives.

    line 44
  8. Distinctive:

    Use the app's existing field components and validation pattern.

    line 53
  9. Very specific:

    Do not recreate menus, popovers, dialogs, or confirmations with absolute positioning and custom click-outside handlers.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 36 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 and Local UI Adapters

Use the components already provided by the app. Read the app's design-system configuration, Toolkit provider, and local UI components before adding or changing a control. Their exports, variants, and props are the contract; do not guess from upstream examples.

Keep imports behind the local adapter

Product pages and domain components should import standard controls through the app's configured local UI alias. In the Chat starter, that is @/components/ui/*; its app/components/ui/button.tsx is a one-line re-export of @agent-native/toolkit/ui/button. Follow an adjacent local shim when the app needs another Toolkit primitive that is already exported there.

Use the app's configured design system and provider mapping for controls passed to shared Toolkit surfaces. For shared Toolkit feature presentation, use the semantic components exposed by @agent-native/toolkit/design-system; keep the feature behavior in its existing controller and customize only its supported presentation seam.

Compose existing controls

  • Prefer a primitive's built-in variant and size. Put page layout on a parent instead of overriding shared component appearance for one screen.
  • Use the app's semantic theme tokens for reusable UI, such as bg-background, text-muted-foreground, border-border, and bg-primary. Keep theme values in the app's existing CSS theme file.
  • Use the control that matches the choice: Switch for a binary setting, Checkbox for independent multi-select, RadioGroup for one choice from a short set, and Select or the app's combobox for a longer predefined list.
  • Compose cards and form fields from the primitives already available. Avoid adding explanatory copy that repeats a visible title or label; see frontend-design for the app's surface-density rules.
  • Put selectable items inside their menu or list group primitives. Keep tab triggers inside the tab list. Supply an accessible title to dialog, sheet, drawer, and alert-dialog content.
  • Match the trigger API to the actual local component. Toolkit wrappers may expose a different API from the upstream primitive; inspect its props before using options such as asChild or render.

Keep controls operable

Use the app's existing field components and validation pattern. Associate errors with their inputs and expose invalid state to assistive technology. Icon-only actions need an accessible name and a usable focus target. Use the icon package already installed by the app.

Do not recreate menus, popovers, dialogs, or confirmations with absolute positioning and custom click-outside handlers. Never use browser alert, confirm, or prompt; use the app's dialog primitives. Keep overlay focus, keyboard, dismissal, and stacking behavior from the existing primitive.

For small visual refinements, use layout classes and semantic tokens. Avoid raw palette overrides, arbitrary one-off values, and manual overlay z-index unless you are fixing a reproduced bug. Use gap-* for layout spacing and the app's class-merging helper when it has one.

Related skill

  • frontend-design — Product UX, density, visual direction, and responsive behavior.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about BuilderIO/agent-native

The biggest 5 of 61 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 61

Talked about on GitHub and Bluesky (61 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 11

6 more on Bluesky

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