daisyui-optimizer
/daisyui-optimizer
Audit and optimize DaisyUI (Tailwind CSS component plugin, daisyui 5.x) usage in a codebase for DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin, bundle/import cost, runtime and re-render cost, theming/SSR, accessibility/forms, copy-in or version drift, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin or "optimize my UI" -- even if they never say "au
- Author
- RuneStone-Tech ↗
- Repository
- optimize-anything ↗
- Licence
- MIT
- Last repository change
- 04.11.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/audit.py
What it does and when to use it
Audit and optimize DaisyUI (Tailwind CSS component plugin, daisyui 5.x) usage in a codebase for DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin, bundle/import cost, runtime and re-render cost, theming/SSR, accessibility/forms, copy-in or version drift, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin or "optimize my UI" -- even if they never say "au
Triggers from the description
Original author description
Audit and optimize DaisyUI (Tailwind CSS component plugin, daisyui 5.x) usage in a codebase for DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin, bundle/import cost, runtime and re-render cost, theming/SSR, accessibility/forms, copy-in or version drift, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin or "optimize my UI" -- even if they never say "au
How it works
- Workflow
- Principles
- Docs
SKILL.md preview
--- name: daisyui-optimizer description: Audit and optimize DaisyUI (Tailwind CSS component plugin, daisyui 5.x) usage in a codebase for DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin, bundle/import cost, runtime and re-render cost, theming/SSR, accessibility/forms, copy-in or version drift, with real before/after measurement. Always produces a written findings report and a fix plan for approval before touching code. Use this whenever the user mentions DaisyUI, daisyui themes, @plugin daisyui, btn/card/modal/drawer classes, Tailwind 4 plugin or "optimize my UI" -- even if they never say "audit" or "optimize". --- # DaisyUI Optimizer DaisyUI is a Tailwind plugin of component classes plus themes; it has no JS runtime. Cost is theme count, unused component CSS, `@apply` coupling and the behavior you still have to write (modals, dropdowns, drawers). ## Workflow ### 1. Scope (quick) - Find the app root and detect DaisyUI usage: `daisyui 5.x`. Record the version, framework (React/Next/Vue/Svelte/Solid/Angular or HTML), styling system, and whether the library is a package, a CSS-only kit, or copied source. - Run `python <skill-dir>/scripts/audit.py <project-root>` -- static scan of `package.json`, config/CSS files and source for version drift, provider/config drift, import and theme issues, a11y gaps, heavy components and upgrade risk, with file:line evidence. Use `--json` to post-process. - Classify the pain: bundle/import cost, runtime/re-render cost, theming/SSR style flash, accessibility/forms, large tables/lists, or migration/upgrade. Ask which hurts if unclear. - Read `references/tooling.md` once: what can be measured here. - Check the Tailwind 4 CSS entry, the enabled themes and whether interactive components rely on `<dialog>`/custom JS. ### 2. Audit The script finds cheap leads; you find the rest by reading. Read the install/config, the global CSS/theme file, the provider or plugin setup, and the 3-5 most-used components. Load only what applies: | Area | Reference | |------|-----------| | Install, config, provider/plugin, theming, SSR | `references/setup.md` | | Bundle/imports, runtime, a11y/forms, tables, upgrades | `references/optimizations.md` | | Measurement and honest reporting | `references/tooling.md` | **Measure, never guess.** Build for production and measure the real route/bundle. Inspect SSR HTML for style tags and dark-mode flash; run axe/Playwright on dialogs, menus, forms and tables. Component count, bundle bytes and a11y violations are evidence; "feels heavy" is not. Mark each finding **Confirmed** (build/analyzer/axe/code evidence) or **Suspected** (needs measuring). ### 3. Report Fill `assets/report-template.md`, save it as `DAISYUI_OPTIMIZATION_REPORT.md` in the project root, and show the user. Five-line summary, findings table by impact/effort, then per-finding detail (evidence, why it hurts, fix, risk, visual/behavior impact). Group near-duplicates. ### 4. Plan -- then stop for approval Use plan mode: `EnterPlanMode` (load with ToolSearch if deferred), write the plan, present with `ExitPlanMode`; if unavailable show it in chat and wait for an explicit "go". Structure: 1. **Quick wins** -- trim imports, use path imports, add provider/plugin correctly, add missing labels/titles, move heavy components off the initial route, remove per-row overlays, align theme tokens, add SSR style/cache setup. Low risk. 2. **Structural** -- split component boundaries, virtualize tables, lazy-load heavy widgets, consolidate theming, migrate variants/tokens, fix form composition, deduplicate copied components. Name each behavior change. 3. **Heavy** -- major upgrade, primitive-base change, CSS-only to styled kit (or reverse), Tailwind 3 to 4, copy-in registry extraction, SSR architecture. Separately approved. Each step: files touched, expected effect, how to verify, how to roll back. ### 5. Fix Only approved items, in small groups. After each: typecheck, lint, tests, production build, and a visual/axe check on affected components. A break must trace to one change. Do not mix a major migration with optimization edits. If a change alters a public component API, theme tokens or SSR behavior, stop and ask. ### 6. Verify and wrap up Re-measure the same routes/components: route JS/CSS, SSR styles/theme, axe violations, dialog/form keyboard flow, table interaction. State plainly what could not be measured. End with deferred items and one suggested next step. ## Principles - **Themes are bytes.** Enable only shipped themes. - **Class names must be statically visible.** No dynamic construction. - **Behavior is still yours.** Use native elements first. ## Docs - https://daisyui.com/docs/
Files in this package (8)
- LICENSE 1 KB
- README.md 1 KB
- SKILL.md 5 KB
- assets/report-template.md 1 KB
- references/optimizations.md 1 KB
- references/setup.md 1 KB
- references/tooling.md 1 KB
- scripts/audit.py 9 KB
Versions
The database has no other skills named daisyui-optimizer.
Database snapshot: 13.11.2026 · package version 5b70b667099c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 85flowbite-optimizer
Audit and optimize Flowbite (Tailwind components + JS / React wrapper, flowbite 4.x / flowbite-react 0.12.x) usage in a codebase for Flowbite, flowbite-react, data-modal-target, Flowbite Tailwind plugin, Flowbite datepicker/dropdown, bundle/import cost, runtime and re-render… - 85franken-ui-optimizer
Audit and optimize Franken UI (HTML-first UIkit + Lit/Tailwind kit, franken-ui 2.x) usage in a codebase for Franken UI, franken-ui, UIkit 3, uk- attributes, LitElement components, Franken UI Tailwind/Vite plugin, bundle/import cost, runtime and re-render cost, theming/SSR,… - 100daisyui
Guide for daisyUI component library with Tailwind CSS. Use when building UI components, implementing themes, or creating responsive designs with daisyUI. - 100daisyui
Build UI components with daisyUI (Tailwind CSS component library). Provides theme configuration, component patterns, and MCP server integration for accurate daisyUI 5 code generation. Use when creating web interfaces with daisyUI components, configuring themes, or generating… - 90daisyui
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. - 100phoenix-tailwind-daisyui
Use when styling Phoenix 1.8 UI — Tailwind v4 app.css (@source, @plugin, no tailwind.config.js), dynamic classes, daisyUI themes/dark mode, core_components (<.input>, <.button>, <.icon>), Layouts.app, flash, accessibility. Not for LiveView forms/lifecycle or JS hooks (use…