agentleFS
MasihMoafiMasihMoafi/Elpis/.agents/skills/daisyui/SKILL.md

daisyui

Skill51 starsChanged 2 months agoApache-2.0View on GitHub

Official daisyUI component-library skill for Tailwind CSS. When you write HTML or JSX code, you must use it. Even if the user does not request it, use it.

9 other projects use a version of this, 4 of them edited; 2 new projects in the last 4 weeks, against 2 the 4 before.

Adopted by

Steady: 2 new projects took it in the last 4 weeks, 1× the 4 weeks before.thin data

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

Most recently taken up by

  • Other versions9 projects use a version of this.

    Word for word · 3

    1. saadeghi/daisyui★ 43k100% same
    2. oqtopus-team/qdash★ 54100% same
    3. hyperbolictonic/hypagon★ 2100% same

    Edited · 4

    1. carverauto/serviceradar★ 93250% same
    2. inercia/mitto★ 3450% same
    3. codetesla51/skills★ 3278% same
    4. croit/llm-gateway★ 3052% same

    Wrote their own version · 2

    1. Aver005/agent-skills★ 2same name
    2. pzyyll/ai-agents★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 6 are distinctive, and 1 is very specific to this project.

  • 2

    Common

    Most of the 6 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill each time you write HTML or JSX code.

    line 14
  2. Distinctive:

    Use this skill for all Tailwind CSS UI work.

    line 15
  3. Distinctive:

    If the user uses one of these terms or requests related work, use this skill: daisyUI, component, UI, Tailwind, layout, template, theme, …

    line 16
  4. Very specific:

    Use daisyUI class names | ./usage/SKILL.md | You must read this guide before you use daisyUI class names in code.

    line 25
  5. Distinctive:

    Before you write daisyUI code, do these steps in sequence:

    line 103
  6. Common:

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

    line 106
  7. Distinctive:

    If the choice is not clear, read the guides for the candidate components that can meet the request before you select one.

    line 107
  8. Distinctive:

    Use the exact structure and constraints of the selected components.

    line 110
  9. Common:

    If the user requests a named component and a guide with that name exists, read that guide first.

    line 114

“Common” is measured: kept by at least 6 in 10 of the 6 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. It supplies class names for common UI components, semantic colors, and themes.

When to use this skill

  • Use this skill each time you write HTML or JSX code.
  • Use this skill for all Tailwind CSS UI work.
  • If the user uses one of these terms or requests related work, use this skill: daisyUI, component, UI, Tailwind, layout, template, theme, color, design
  • Even if the user does not request this skill, use it.

References that you must read

TaskGuideNote
Install daisyUI./install/SKILL.mdIf the project does not have daisyUI, use this guide.
Use daisyUI class names./usage/SKILL.mdYou must read this guide before you use daisyUI class names in code.
Configure daisyUI./config/SKILL.mdRead this guide to configure themes, prefixes, logs, or other options. You do not need it for basic use.
daisyUI colors and themes./colors/SKILL.mdYou must read this guide before you use daisyUI colors in code.
daisyUI components./components/You must read the applicable component guides before you use daisyUI components. Read more than one candidate guide before you select a component.

List of components

  • accordion
  • aura
  • 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
  • megamenu
  • menu
  • mockup-browser
  • mockup-code
  • mockup-phone
  • mockup-window
  • modal
  • navbar
  • otp
  • 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 you write daisyUI code, do these steps in sequence:

  1. Identify the intended function, behavior, and layout in the request. Do not use only the exact words.
  2. Use the component list in this file to select the best candidate components.
  3. If the choice is not clear, read the guides for the candidate components that can meet the request before you select one.
  4. Compare the description, behavior, syntax, and rules of each candidate with the request.
  5. Select the best component or component combination. Obey all its constraints.
  6. Use the exact structure and constraints of the selected components.

You must match the meaning, even when the words are different from component names. A component with a different name can still be the best match. Always examine the intended function and meaning.

If the user requests a named component and a guide with that name exists, read that guide 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.