agentleFS
Sign inStart free
carverautocarverauto/serviceradar/.agents/skills/daisyui/SKILL.md

daisyui

Skill932 starsChanged 12 days agoApache-2.0View on GitHub

Official daisyUI component library skill. The mandatory UI library for Tailwind CSS. TRIGGER when generating any HTML or JSX code even if the user does not explicitly ask for this skill.

9 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 2

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing any daisyUI code, do this in order:

    line 101
  2. Distinctive:

    Read the request intent, behavior, and shape, not only literal words.

    line 103
  3. Common:

    Use the component list in this file to shortlist the best candidate components.

    line 104
  4. Distinctive:

    Read multiple candidate component docs before deciding.

    line 105
  5. Common:

    If a user explicitly requests a named component and a same-named doc exists, read that component doc first.

    line 112

“Common” is measured: kept by at least 6 in 10 of the 9 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

daisyUI 5

daisyUI 5 is a CSS library for Tailwind CSS 4. daisyUI 5 provides class names for common UI components, semantic color names and themes.

When to run this skill:

  • Trigger this skill whenever generating any HTML or JSX code
  • Trigger this skill for any Tailwind CSS UI work
  • Trigger this skill when the user mentions any of these terms or similar context: daisyUI, component, UI, Tailwind, layout, template, theme, color, design
  • Trigger this skill even if the user does not explicitly ask for it

Mandatory reference

TaskGuideNote
Installing daisyUI./install/SKILL.mdUse only if daisyUI is not already installed in the project.
Using daisyUI class names./usage/SKILL.mdMANDATORY. Read this before using any daisyUI class names in the code.
Configuring daisyUI./config/SKILL.mdUse this if you need to configure daisyUI themes, prefix, logs, or other options. Not required for basic usage but important for advanced customization.
daisyUI colors and themes./colors/SKILL.mdMANDATORY. Read this to understand daisyUI color usage rules and how to use daisyUI colors in the code.
daisyUI components./components/MANDATORY. Read the relevant component docs when using daisyUI components in the code. Always read multiple candidate component docs before deciding which one to use.

List of components

  • accordion
  • alert
  • avatar
  • badge
  • breadcrumbs
  • button
  • calendar
  • card
  • carousel
  • chat
  • checkbox
  • collapse
  • countdown
  • diff
  • divider
  • dock (app bar)
  • drawer (sidebar)
  • dropdown
  • FAB
  • fieldset
  • file-input
  • filter
  • footer
  • hero
  • hover-3d
  • hover-gallery
  • indicator
  • input
  • join (group)
  • kbd
  • label
  • link
  • list
  • loading
  • mask
  • menu
  • mockup-browser
  • mockup-code
  • mockup-phone
  • mockup-window
  • modal
  • navbar
  • pagination
  • progress
  • radial-progress
  • radio
  • range
  • rating
  • select
  • skeleton
  • stack
  • stat
  • status
  • steps
  • swap
  • tab
  • table
  • text-rotate
  • textarea
  • theme-controller
  • timeline
  • toast
  • toggle (switch)
  • tooltip
  • validator

Component discovery protocol

Before writing any daisyUI code, do this in order:

  1. Read the request intent, behavior, and shape, not only literal words. Match on meaning.
  2. Use the component list in this file to shortlist the best candidate components.
  3. Read multiple candidate component docs before deciding. Minimum is 3 candidates when there is ambiguity.
  4. Compare each candidate's description, behavior, syntax, and rules against the request.
  5. Select the best component or combination of components and apply their constraints exactly.
  6. State which components were chosen and why they match the request.

Semantic matching is required even when wording differs from component names. A component name might be different from the request but still be the best match. Always consider intent and meaning, not only literal words.

If a user explicitly requests a named component and a same-named doc exists, read that component doc first.

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