Skip to content
cccskills
FreePublished on GitHub

daisyui-usage

MANDATORY usage rules for daisyUI 5

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39 stars(GitHub 39 + cccskills 0)

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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
  12. Always use the default variant of daisyUI components unless the user asked for a specific variant or color. For example when you need a button, do not use btn btn-primary, prefer btn, unless the user asked for a specific variant.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

[OMX] Run an anti-slop cleanup/refactor/deslop workflow

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

[OMX] 只读调查跨文件的行为、原因或架构问题,提供源码证据与不确定性。单文件查找无需此流程。

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

ask

Free

[OMX] Ask a local external advisor CLI (Claude or Gemini) and capture a reusable artifact

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

[OMX] Supervise deep interview, consensus planning, and durable goal execution for explicit hands-off delivery.

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

[OMX] Stateful validator-gated research loop with native-hook persistence

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

[OMX] Bounded best-practice research wrapper using official/upstream evidence first

The English summary is being prepared. Showing the original description.

Tenon-Net/TenonAdmin39Updated Oct 23, 2026

See all skills by Tenon-Net

Report a problem with this skill