菜单
Configuration options for daisyUI 5
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Verify Linear backlog tickets against the actual codebase before anyone implements them — extract each ticket's checkable claims, grep the code to confirm or refute, classify by scope, and leave an evidence-backed triage comment. Use when the user says "triage the backlog", "comb through Linear tasks", "verify these tickets", "/linear-triage", or on a schedule. Not for implementing fixes (use linear-to-pr on tickets triaged valid), and never changes ticket state beyond commenting unless explicitly told to.
Verify any UI-affecting change end-to-end before declaring it done — boot the app, interact with the change via Playwright, capture before/after screenshots (light/dark, desktop/phone), check console errors, and attach the evidence. Use after implementing or reviewing any change to components, routes with visible output, layouts, styling, or theming. Triggers include "verify this UI change", "did the banner/button/layout change work", or finishing any *.tsx edit that alters rendered markup or classes. Not for server-only changes (models, API routes, env plumbing), docs, or pure test edits.
Explore the running Iridium app like a curious, destructive user and file GitHub issues for confirmed bugs. Picks an exploration charter (auth, notes, chat, settings, admin, mobile), drives the app with Playwright, reproduces every finding twice, dedupes against open qa-explorer issues, and files structured reports with repro scripts. Use when the user says "qa sweep", "explore the app for bugs", "run the qa explorer", "hunt for bugs", or "do some exploratory testing". Not for implementing fixes (use github-issue-to-pr on the filed issues), not for deterministic regression tests (those live in tests/), and never against production.
Drive a GitHub issue to an open pull request. Fetches the issue with gh, self-assigns, creates a linked branch via gh issue develop, implements the change, runs validation plus targeted Playwright e2e tests, captures screenshots of UI changes and links them from the PR body, and opens the PR with a closing "Fixes
Drive a Linear issue to an open GitHub pull request. Fetches the issue, branches using Linear's suggested branch name, implements the change, runs validation plus targeted Playwright e2e tests, captures screenshots of UI changes and links them from the PR body, opens the PR with gh, and moves the issue to a review status. Use when the user says "work on ABC-123" (any Linear issue identifier), "take this Linear issue to a PR", "implement this ticket", "linear to pr", or pastes a linear.app issue URL to be implemented. Not for creating or triaging Linear issues, and not for reviewing or merging existing PRs.
MANDATORY color usage rules for daisyUI 5
| name | daisyui-config |
| description | Configuration options for daisyUI 5 |
daisyUI 5 config docs: https://daisyui.com/docs/config/ daisyUI without config:
@plugin 'daisyui';
daisyUI config with light theme only:
@plugin 'daisyui' {
themes: light --default;
}
daisyUI with all the default configs:
@plugin 'daisyui' {
themes:
light --default,
dark --prefersdark;
root: ':root';
include:;
exclude:;
prefix:;
logs: true;
}
An example config:
In below config, all the built-in themes are enabled while bumblebee is the default theme and synthwave is the prefersdark theme (default dark mode)
All the other themes are enabled and can be used by adding data-theme="THEME_NAME" to the <html> element
root scrollbar gutter is excluded. daisy- prefix is used for all daisyUI classes and console.log is disabled
@plugin 'daisyui' {
themes:
light,
dark,
cupcake,
bumblebee --default,
emerald,
corporate,
synthwave --prefersdark,
retro,
cyberpunk,
valentine,
halloween,
garden,
forest,
aqua,
lofi,
pastel,
fantasy,
wireframe,
black,
luxury,
dracula,
cmyk,
autumn,
business,
acid,
lemonade,
night,
coffee,
winter,
dim,
nord,
sunset,
caramellatte,
abyss,
silk;
root: ':root';
include:;
exclude: rootscrollgutter, checkbox;
prefix: daisy-;
logs: false;
}