agentleFS
Sign inStart free
Kainiko943Kainiko943/beautiful-ui/framework-shadcn-tailwind-ui/SKILL.md

framework-shadcn-tailwind-ui

Skill4 starsChanged 7 months agoMITView on GitHub

Use with beautiful-ui and platform-web-ui when the target web app uses shadcn/ui components, Tailwind CSS utilities, or a React component system built from copied component source.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this adapter after beautiful-ui and platform-web-ui when implementation should land in a shadcn/ui + Tailwind codebase.

    line 10
  2. Distinctive:

    Treat shadcn/ui as editable source, not a black-box component library.

    line 24
  3. Distinctive:

    Use existing local components before adding new shadcn components.

    line 25
  4. Distinctive:

    Prefer component variants for repeated states such as intent, density, size, loading, invalid, and selected.

    line 27
  5. Very specific:

    Use data-* attributes, aria-* attributes, and visible focus styles for stateful controls.

    line 28
  6. Distinctive:

    Keep class strings readable.

    line 29
  7. Very specific:

    Do not turn every surface into a Card.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Framework Shadcn Tailwind UI

Overview

Use this adapter after beautiful-ui and platform-web-ui when implementation should land in a shadcn/ui + Tailwind codebase. Preserve the product-specific visual direction, then express it through local components, tokens, variants, and stateful composition.

Current Setup Notes

As of April 26, 2026, shadcn/ui recommends shadcn/create or shadcn@latest init -t [framework] for supported frameworks, with existing-project setup handled through the official framework guide. Tailwind CSS v4 uses CSS-first configuration and @import "tailwindcss" in new installs. Verify official docs before giving exact setup commands in generated project work.

Official references:

Rules

  • Treat shadcn/ui as editable source, not a black-box component library.
  • Use existing local components before adding new shadcn components.
  • Define theme tokens in CSS variables or the repo's established Tailwind setup before adding one-off utility piles.
  • Prefer component variants for repeated states such as intent, density, size, loading, invalid, and selected.
  • Use data-* attributes, aria-* attributes, and visible focus styles for stateful controls.
  • Keep class strings readable; extract variants or local wrappers when repeated class combinations carry product meaning.
  • Do not turn every surface into a Card; reserve cards for repeated objects, tools, modals, and framed content.

Handoff Must Include

  • Components to add or reuse.
  • Token changes and where they belong.
  • Variant names for recurring states.
  • Tailwind layout constraints for desktop and mobile.
  • Accessibility attributes and focus behavior.
  • Verification commands and screenshot targets.

Read These References

  • references/component-patterns.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.

Check your setup, free