agentleFS
skeletonlabsskeletonlabs/skeleton/.agents/skills/create-tailwind-utility/SKILL.md

create-tailwind-utility

Skill6.1k starsChanged 4 days agoMITView on GitHub

Scaffold a new Tailwind utility (CSS-only utility class) in the Skeleton core package, following @utility conventions used by buttons, badges, cards, etc.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 2 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 4 mentionsJul 2026: 6 mentionsAug 2026: 4 mentionsSep 2026: 1 mentionOct 2026: 4 mentionsNov 2026: 11 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the skeletonlabs/skeleton repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about skeletonlabs/skeleton

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

See all 53

Talked about on GitHub, Hacker News and Bluesky (53 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

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

    Import registry: packages/skeleton/src/index.css — every new file must be added here

    line 13
  2. Distinctive:

    Ask one at a time, confirm each, write nothing until all are answered and the user confirms.

    line 37
  3. Very specific:

    Add the new file's @import to packages/skeleton/src/index.css.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Create Tailwind Component

Scaffold a new CSS-only utility class in the Skeleton core package at packages/skeleton/src/utilities/. Tailwind v4 @utility syntax.

Where things live

  • Utilities source: packages/skeleton/src/utilities/
  • Import registry: packages/skeleton/src/index.css — every new file must be added here
  • Reference files to model after:
    • Tailwind Utility: masks.css
    • Tailwind Component: buttons.css, badges.css, cards.css, chips.css
    • Form-related: form-inputs.css, form-selects.css, etc.
    • Typography: typography.css

File destination rules

Recommend placement based on feature type, explain the reasoning, accept overrides.

  • Tailwind Utility → extend utilities/masks.css. Document under design/masks.mdx.
  • Tailwind Component → new file at utilities/<plural-name>.css (e.g. buttons.css). Document under tailwind-components/<plural-name>.mdx modeled after buttons.mdx.

Conventions (from buttons.css / badges.css)

  • Top comment: /* Components: <Name> */ or /* Utilities: <Name> */
  • Base utility uses kebab-case class name: @utility <name> { ... }
  • Variants use suffixes: <name>-<modifier> (e.g. btn-icon, badge-dot)
  • Sizes use --element-size-{xs,sm,base,lg,xl, ...} design tokens; expose them via local CSS vars (--btn-size) so size variants override cleanly
  • Wrap interactive states in @variant not-disabled { @variant hover { ... } }

Prompt flow

Ask one at a time, confirm each, write nothing until all are answered and the user confirms.

  1. Feature name — singular concept; derive the utility class (kebab-case singular, e.g. btn, badge) and the CSS filename (plural, e.g. buttons.css). Recommend both, accept overrides.
  2. Goal — one-line description of what the component does and when to reach for it.
  3. Target HTML element(s) — what the user is expected to apply this class to (e.g. <button>, <a>, <span>, <input>).
  4. Category — utility, component → resolves file destination per the rules above. Surface the existing file option when a form/typography fit exists.
  5. Design requirements — size variants? icon variant? state variants (active, disabled)? group wrapper? Anything else (radius, transitions, hover behavior).
  6. Confirm — show the planned file path, utility class names, and design-token usage before writing.

After scaffolding

  1. Add the new file's @import to packages/skeleton/src/index.css. Order matches the existing alphabetical-ish grouping.
  2. Trigger /create-doc to scaffold the documentation page. Pass along the utility name and CSS filename so the doc skill can derive the doc slug per its naming conventions.

Final summary

List: file path, utility or component class names defined, the index.css import line added, and the doc page that /create-doc will scaffold next.

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.