
Daisyui
Ship Tailwind CSS 4 UIs faster by giving your agent official daisyUI 5 component class names and install patterns instead of hand-rolling every button, modal, and form.
Overview
daisyUI is an agent skill for the Build phase that applies official daisyUI 5 + Tailwind CSS 4 component classes and install rules while you implement frontend HTML.
Install
npx skills add https://github.com/saadeghi/daisyui --skill daisyuiWhat is this skill?
- Official daisyUI 5 reference aligned with Tailwind CSS 4 (`@import "tailwindcss"` + `@plugin "daisyui"`; no `tailwind.co
- Class-name recipes for common UI components (buttons, cards, modals, forms) without custom CSS sprawl
- Install paths: npm dev dependency and optional CDN + Tailwind browser v4 snippet
- Links to v5 docs, editor guide, release notes, and v4→v5 upgrade guide
- Usage rules: compose daisyUI utility classes on HTML elements per library conventions
- Requires Tailwind CSS 4
- Official daisyUI skill metadata version 5.5.x
- Tailwind v4 deprecates tailwind.config.js for typical Node setups
Adoption & trust: 1.2k installs on skills.sh; 41.1k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps mixing Tailwind 3 config with Tailwind 4, or guesses wrong class names for standard UI components.
Who is it for?
Solo builders already on Tailwind 4 who want DaisyUI components in pages, layouts, and prototypes without reading the full docs each session.
Skip if: Teams on Tailwind 3-only stacks unwilling to upgrade, native mobile-only UI (Swift/Kotlin), or projects that forbid utility-class component libraries.
When should I use this skill?
Building or refactoring HTML/CSS UI with Tailwind CSS 4 and daisyUI component classes.
What do I get? / Deliverables
Frontend markup follows daisyUI 5 conventions with a correct CSS entry (`@import "tailwindcss"` and `@plugin "daisyui"`) and consistent component classes ready to ship.
- Correct daisyUI class usage in markup
- Valid Tailwind 4 + daisyUI CSS bootstrap snippet
Recommended Skills
Journey fit
How it compares
Reference skill for a CSS component plugin—not a Figma-to-code generator or a full design-system MCP.
Common Questions / FAQ
Who is daisyUI for?
Indie and solo web builders using Tailwind CSS 4 who want their coding agent to output valid daisyUI 5 markup and setup.
When should I use daisyUI?
During Build (frontend) when scaffolding dashboards, forms, modals, and marketing pages with Tailwind 4 and you need correct daisyUI class names and install snippets.
Is daisyUI safe to install?
Review the Security Audits panel on this Prism page and the upstream saadeghi/daisyui skill source before trusting it in your repo.
SKILL.md
READMESKILL.md - Daisyui
# daisyUI 5 daisyUI 5 is a CSS library for Tailwind CSS 4 daisyUI 5 provides class names for common UI components - [daisyUI 5 docs](http://daisyui.com) - [Guide: How to use this file in LLMs and code editors](https://daisyui.com/docs/editor/) - [daisyUI 5 release notes](https://daisyui.com/docs/v5/) - [daisyUI 4 to 5 upgrade guide](https://daisyui.com/docs/upgrade/) ## daisyUI 5 install notes [install guide](https://daisyui.com/docs/install/) 1. daisyUI 5 requires Tailwind CSS 4 2. `tailwind.config.js` file is deprecated in Tailwind CSS v4. do not use `tailwind.config.js`. Tailwind CSS v4 only needs `@import "tailwindcss";` in the CSS file if it's a node dependency. 3. daisyUI 5 can be installed using `npm i -D daisyui@latest` and then adding `@plugin "daisyui";` to the CSS file 4. daisyUI is suggested to be installed as a dependency but if you really want to use it from CDN, you can use Tailwind CSS and daisyUI CDN files: ```html <link href="https://cdn.jsdelivr.net/npm/daisyui@5" rel="stylesheet" type="text/css" /> <script src="https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4"></script> ``` 5. A CSS file with Tailwind CSS and daisyUI looks like this (if it's a node dependency) ```css @import "tailwindcss"; @plugin "daisyui"; ``` ## daisyUI 5 usage rules 1. We can give styles to a HTML element by adding daisyUI class names to it. By adding a component class name, part class names (if there's any available for that component), and modifier class names (if there's any available for that component) 2. Components can be customized using Tailwind CSS utility classes if the customization is not possible using the existing daisyUI classes. For example `btn px-10` sets a custom horizontal padding to a `btn` 3. If customization of daisyUI styles using Tailwind CSS utility classes didn't work because of CSS specificity issues, you can use the `!` at the end of the Tailwind CSS utility class to override the existing styles. For example `btn bg-red-500!` sets a custom background color to a `btn` forcefully. This is a last resort solution and should be used sparingly 4. If a specific component or something similar to it doesn't exist in daisyUI, you can create your own component using Tailwind CSS utility 5. when using Tailwind CSS `flex` and `grid` for layout, it should be responsive using Tailwind CSS responsive utility prefixes. 6. Only allowed class names are existing daisyUI class names or Tailwind CSS utility classes. 7. Ideally, you won't need to write any custom CSS. Using daisyUI class names or Tailwind CSS utility classes is preferred. 8. suggested - if you need placeholder images, use https://picsum.photos/200/300 with the size you want 9. suggested - when designing , don't add a custom font unless it's necessary 10. don't add `bg-base-100 text-base-content` to body unless it's necessary 11. For design decisions, use Refactoring UI book best practices daisyUI 5 class names are one of the following categories. These type names are only for reference and are not used in the actual code - `component`: the required component class - `part`: a child part of a component - `style`: sets a specific style to component or part - `behavior`: changes the behavior of component or part - `color`: sets a specific color to component or part - `size`: sets a specific size to component or part - `placement`: sets a specific placement to component or part - `direction`: sets a specific direction to component or part - `modifier`: modifies the component or part in a specific way - `variant`: prefixes for utility classes that conditionally apply styles. syntax is `variant:utility-class` ## Config daisyUI 5 config docs: https://daisyui.com/docs/config/ daisyUI without config: ```css @plugin "daisyui"; ``` daisyUI config with `light` theme only: ```css @plugin "daisyui" { themes: light --default; } ``` daisyUI with a