--- title: "daisyUI — AI affordances" description: "daisyUI is the most AI-forward system in this study outside of shadcn/ui, and the only one that has turned AI consumption into a commercial product line. Its…" url: "https://state-of-ai-in-design-systems.netlify.app/systems/daisyui.md" canonical: "https://state-of-ai-in-design-systems.netlify.app/systems/daisyui" type: "design-system-record" json: "https://state-of-ai-in-design-systems.netlify.app/systems/daisyui.json" id: "daisyui" category: "component-library" ai_maturity: "ai-native" affordance_count: 9 technique_count: 8 data_collected: "2026-07-26/27" generated: "2026-07-28T06:01:02Z" report: "State of AI in Design Systems — July 2026" author: "Kaelig Deloumeau-Prigent" license: "CC-BY-4.0" citation: "Deloumeau-Prigent, K. (2026). State of AI in Design Systems. https://state-of-ai-in-design-systems.netlify.app/systems/daisyui.md" --- > Snapshot of 2026-07-27. Every claim below links to the source URL it was taken from. Check the source before citing. # daisyUI — AI affordances Saadeghi (open source) · component-library · MIT (library + skill); daisyUI Blueprint MCP server is proprietary/paid · AI maturity: **ai-native** (AI consumption is a design goal, with dedicated surfaces and staff behind it). 9 affordances, 8 coercion techniques. - Docs: https://daisyui.com - Repo: https://github.com/saadeghi/daisyui - This record as JSON: https://state-of-ai-in-design-systems.netlify.app/systems/daisyui.json - This record on the site: https://state-of-ai-in-design-systems.netlify.app/systems/daisyui ## Summary daisyUI is the most AI-forward system in this study outside of shadcn/ui, and the only one that has turned AI consumption into a commercial product line. Its consumption surface is deep and layered: a single `llms.txt` that is simultaneously a Cursor rule, an agent skill and a docs digest (complete with `alwaysApply: true` frontmatter and “TRIGGER ... even if the user does not explicitly ask” language); an MIT-licensed multi-file skill in `skills/daisyui/` with a “Mandatory reference” routing table; native agent-plugin manifests for Claude Code, Codex, Cursor and Grok Build (plus a generic `.agents/plugins/marketplace.json`); and “Blueprint” 1.5, a paid, license-keyed official MCP server (npm `daisyui-blueprint@1.5.3`) whose marketing copy is an explicit thesis that skills fail because “the model reads a few files, skips the rest, ignores inconvenient rules, and moves on.” Blueprint answers that with six sequenced tools (Setup Expert, Rules Enforcer, Creative Director, Page Architect, Component Syntax Expert, Quality Inspector), three of them labelled “Mandatory” and the last a “Final gate” the agent must pass before it may call the page finished. The builder side is thinner but real: six path-scoped Copilot `*.instructions.md` files that themselves mandate Context7 MCP for syntax lookups, with no CLAUDE.md or AGENTS.md in the repo. ## Maintenance - Actively maintained: yes - Last release: v5.7.4, 2026-07-25 (v5.7.2/.3/.4 all shipped the same day) - Activity: 41,846 stars, MIT, not archived. Last commit 2026-07-27T03:04Z; ≥100 commits in the trailing 90 days (API page cap hit). Blueprint MCP npm package `daisyui-blueprint` created 2025-10-24, 29 versions, latest 1.5.3 published 2026-07-24, so the AI product ships on the same cadence as the library. Single-maintainer bus factor (Pouya Saadeghi) is the main structural risk. ## AI affordances (9) ### daisyUI Blueprint MCP (v1.5) Type: `mcp-server` (MCP server) · Official · Audience: consumers The official daisyUI MCP server, sold as a paid product ($22/mo, $45/quarter, yearly and lifetime licenses; 3-day trial). Installed as `npx -y daisyui-blueprint@latest` with LICENSE + EMAIL env vars and an optional FIGMA API key. Exposes six sequenced tools (Setup Expert, Rules Enforcer, Creative Director, Page Architect, Component Syntax Expert, Quality Inspector), plus MCP resources (Snippet, Setup, Rule, Page) and prompt-tools for Figma→daisyUI, Tailwind→daisyUI, Bootstrap→daisyUI, Screenshot→daisyUI and image-palette→daisyUI theme. Claims ‘168 rules and principles’, ‘211 page architectures’, ‘68 components’. Dedicated install pages for Cursor, Claude Code, Codex, Grok Build, VSCode Copilot, OpenCode, Antigravity, Cline, Windsurf, OpenClaw, Claude Desktop, Zed. - Docs: https://daisyui.com/blueprint/ - Code: https://www.npmjs.com/package/daisyui-blueprint Notes: Source is closed: the npm package has no `repository` field and no license field; tool schemas could not be independently inspected without a license key. Version 1.5 changelog dated July 2026. ```bash claude mcp add daisyui-blueprint --env LICENSE=YOUR_LICENSE_KEY --env EMAIL=YOUR_EMAIL --env FIGMA=YOUR_FIGMA_API_KEY -- npx -y daisyui-blueprint@latest ``` Source: https://daisyui.com/blueprint/claudecode/ ### Official daisyUI skill (skills/daisyui/) Type: `claude-skill` (Agent skill) · Official · Audience: consumers MIT-licensed, in-repo multi-file skill: a root SKILL.md router plus install/, usage/, config/, colors/ sub-skills and ~70 per-component reference files under components/. Install via `npx skills add saadeghi/daisyui`, or per-agent guides for VSCode Copilot, Claude Code, Codex, Grok Build, Cursor, OpenCode, OpenClaw, Windsurf, Gemini CLI, Antigravity. Notably, daisyUI’s own docs de-recommend it in favour of MCP: the skill page argues MCP servers are ‘preferable to skills, offering better efficiency and token savings by providing context on-demand rather than as static files.’ - Docs: https://daisyui.com/docs/skill/ - Code: https://github.com/saadeghi/daisyui/tree/master/skills/daisyui ```markdown --- name: daisyui description: Official daisyUI component library skill. The mandatory UI library for Tailwind CSS. TRIGGER when generating any HTML or JSX code even if the user does not explicitly ask for this skill. metadata: version: 5.7.x source: https://daisyui.com/SKILL.md --- ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/skills/daisyui/SKILL.md ### daisyui.com/llms.txt Type: `llms-txt` (llms.txt) · Official · Audience: consumers A ~79 KB single-file digest of the whole library (install matrix for 35 frameworks, usage rules, class-name taxonomy, config, colors/themes, per-component syntax). It is not a plain llms.txt: it ships YAML frontmatter with `alwaysApply: true` and `applyTo: "**"`, so the exact same file works as a Cursor `.mdc` rule, a skill, or an @docs source. The Cursor setup page tells you to `curl` it straight into `.cursor/rules/daisyui.mdc`. - Docs: https://daisyui.com/docs/editor/cursor/ - Code: https://daisyui.com/llms.txt Notes: No /llms-full.txt (404). No per-page .md variants (/components/button.md → 404); instead each docs page has a ‘Text version for AI prompts’ link pointing at the raw GitHub source of the page’s +page.md. ```yaml --- name: daisyui description: Official daisyUI component library skill. The mandatory UI library for Tailwind CSS. TRIGGER when generating any HTML or JSX code even if the user does not explicitly ask for this skill. metadata: version: 5.7.x source: https://daisyui.com/llms.txt alwaysApply: true applyTo: "**" --- ``` Source: https://daisyui.com/llms.txt ### Agent-plugin marketplaces (.claude-plugin, .codex-plugin, .cursor-plugin, .grok-plugin, .agents) Type: `registry` (Registry) · Official · Audience: consumers The repo root carries five parallel plugin/marketplace manifests so daisyUI is installable as a first-class plugin in Claude Code, Codex, Cursor, Grok Build and the generic `.agents` format. The Claude marketplace lists two plugins side by side: the free skill and the paid Blueprint MCP. `defaultEnabled: true` in the Claude plugin manifest means the skill is active on install without user opt-in. - Docs: https://daisyui.com/docs/plugin/ - Code: https://github.com/saadeghi/daisyui/blob/master/.claude-plugin/marketplace.json ```json { "name": "daisyui", "description": "Official daisyUI plugins for Claude Code", "owner": { "name": "daisyUI" }, "plugins": [ { "name": "daisyui", "source": "./", "description": "daisyUI component library skill" }, { "name": "daisyui-blueprint", "source": "./packages/blueprint", "description": "daisyUI Blueprint MCP server - (Needs paid license)" } ] } ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/.claude-plugin/marketplace.json ### Editor/LLM setup docs + /ai landing page Type: `ai-docs-page` (AI docs page) · Official · Audience: consumers `/docs/editor/` is a ‘Code editors and LLM setup’ hub with per-tool pages for VSCode, Cursor, Zed, Windsurf, Claude Desktop, Claude Code, ChatGPT, Gemini, Grok and Cline. Each page distributes llms.txt three ways (one-shot @web prompt, permanent .cursor/rules file, custom-docs registration) then upsells Blueprint. Separately `/ai/` is a marketing/SEO landing page (‘AI UI generation with daisyUI’) whose pitch is the design-system argument in miniature: 'AI can create a screen quickly. Revisions become harder when every component is a new utility-class recipe. daisyUI gives models readable component names they can reuse across prompts and pages.' - Docs: https://daisyui.com/docs/editor/ ```bash Run this command to save the llms.txt file to .cursor/rules/daisyui.mdc curl -L https://daisyui.com/llms.txt --create-dirs -o .cursor/rules/daisyui.mdc ``` Source: https://daisyui.com/docs/editor/cursor/ ### Paid Dashboard Skill and Charts Skill Type: `claude-skill` (Agent skill) · Official · Audience: consumers daisyUI sells agent skills as products alongside the free one: ‘Dashboard Skill — Expert in generating layouts and UI blocks for dashboards and admin panels, based on daisyUI style, from $29’ and ‘Charts Skill — Expert in generating all kind of charts and graphs, based on daisyUI style, from $39’. The page’s headline is ‘Enough with AI slop 🙅 Setup your coding agent to generate better UI.’ This is one of the few examples in the study of agent skills as a monetised SKU. - Docs: https://daisyui.com/skills/ ```text Official daisyUI Skills Enough with AI slop 🙅 Setup your coding agent to generate better UI. Compatible with all coding agents daisyUI Skill — Generates daisyUI components and themes — Free Dashboard Skill — Expert in generating layouts and UI blocks for dashboards and admin panels, based on daisyUI style — from $29 Charts Skill — Expert in generating all kind of charts and graphs, based on daisyUI style — from $39 ``` Source: https://daisyui.com/skills/ ### .github/instructions/*.instructions.md (6 files) Type: `copilot-instructions` (Copilot instructions) · Official · Audience: builders The repo has no CLAUDE.md and no AGENTS.md; instead it uses GitHub Copilot’s path-scoped instructions format with six files: code_generation, code_generation_with_git, communication, packages.daisyui, packages.docs, workspace. They encode hard prohibitions (‘Never ever break the code syntax’, ‘Never ever delete files before asking’, ‘Do not add any new package or dependency without asking first’), no-go directories (‘packages/bundle ... Do not read nor write code here’), and mandate an external MCP server as the source of truth for syntax rather than model memory. - Code: https://github.com/saadeghi/daisyui/tree/master/.github/instructions ```markdown --- applyTo: "**" --- # Code Generation Rules ## General rules - Never ever break the code syntax - If you are asked to write code, only write the code, do not add any explanations unless necessary - do not make up answers. For code, always search the docs and write code based on that - If you're not sure about the syntax Use Context7 MCP server ## Finding information - Use Context7 MCP server to find information about packages, libraries, and languages. Context7 MCP server provides up-to-date and accurate information - Search official documentation if needed - You can search into related files to find patterns and examples ## Writing code - Do not guess, do not hallucinate, write code based on the information and facts you have, if you don't have enough information, ask for more information ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/.github/instructions/code_generation.instructions.md ### npx skills add saadeghi/daisyui Type: `cli-scaffolding` (CLI scaffolding) · Official · Audience: consumers Generic one-command skill install for agents without a bespoke setup page, using the community `skills` CLI against the repo’s skills/ directory. - Docs: https://daisyui.com/docs/skill/ ### Community daisyUI MCP servers (birdseyevue/daisyui-mcp et al.) Type: `mcp-server` (MCP server) · Community · Audience: consumers A cluster of small community MCP servers wrap daisyUI docs, most of them by scraping the official llms.txt. Largest is birdseyevue/daisyui-mcp (77 stars, pushed 2026-07-12): ‘A token-friendly local MCP server for DaisyUI component documentation using their public llms.txt.’ Others: SidiqHadi/daisyui-mcp (4), ralscha/daisyui-mcp (2, active 2026-07-27), matracey/daisyui-mcp-server (2, ‘MCP server for daisyUI React components’), theHamdiz/daisy-days (1). All are small and none is endorsed by the maintainer; the official docs instead point unlicensed users at Context7 or ‘daisyUI GitMCP’. - Code: https://github.com/birdseyevue/daisyui-mcp Notes: Star counts and push dates from GitHub search API on 2026-07-27. ## Coercion techniques (8) ### “Mandatory MCP workflow” — tool-gated sequential pipeline with a terminal quality gate Category: `tool-gating` (Tool-gating) · all 20 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/tool-gating.md Blueprint’s central coercion device. Rather than trusting the model to read rules, it decomposes UI generation into six tools with a fixed execution order, three explicitly labelled ‘Mandatory’ and one labelled ‘Final gate’. Context is withheld until the corresponding tool is called, and the Quality Inspector produces a repair list the agent must clear before it may declare completion. This is the strongest anti-skimming architecture observed in the study: it converts instructions the model can ignore into tool calls it cannot skip. ```text THE REAL SOLUTION Blueprint fixes that. Introducing a mandatory MCP workflow. Every tool has a defined job and a strict execution order. Each tool provides the necessary resources and functionality to your agent. The agent must follow these rules sequentially. It cannot skip steps, invent component syntax, or mark unfinished work as complete. 01 Mandatory — Setup Expert 02 Mandatory — Rules Enforcer Loads implementation, syntax, accessibility, responsive, theme, media, and quality rules as requirements your LLM must follow. The workflow cannot continue by skimming half a skill file and quietly dropping the difficult constraints. 05 Mandatory — Component Syntax Expert Retrieves exact, correct daisyUI component structures, variants, code snippets, and examples only when the page needs them. No stale syntax from model memory. No utility pile pretending to be a maintained component. 06 Final gate — Quality Inspector When the inspection finds a problem, your agent has to fix it before the workflow can call the page finished. ``` Source: https://daisyui.com/blueprint/ ### Named the failure mode: “Your LLM ignores the instructions and skills” Category: `validation-loop` (Validation loop) · all 29 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/validation-loop.md daisyUI’s marketing is an unusually explicit, receipts-first critique of the skill/rules paradigm every other system in this study relies on, complete with a mocked-up log of a model reading SKILL.md, truncating two reference files at ‘Lines 1 to 120’, partially ignoring four more and skipping quality-checks.md entirely. It is the clearest articulation in the dataset of *why* prohibition-style instruction files under-perform, and it is used to justify moving enforcement from prose into tool boundaries. ```text TRYING TO FIX THE SLOP WITH INSTRUCTIONS? Your LLM ignores the instructions and skills. Agent skills are collections of instructions and rules. Check the logs and the pattern is familiar: the model reads a few files, skips the rest, ignores inconvenient rules, and moves on. UI work needs more context than most tasks. Yet as the instruction set grows, the chance of selective reading grows with it. Skill files inspected Ignored 40% of the rules Skipped 23 files due to overconfidence Ignored the rules and treated them as suggestions only SKILL.md read references/components.md Lines 1 to 120 references/themes.md Lines 1 to 120 references/design.md partially ignored references/anti-patterns.md partially ignored references/accessibility.md partially ignored references/responsive.md partially ignored references/quality-checks.md skipped ! The model continued without following the rules it was expected to follow. Wasted time, wasted effort, wasted tokens ``` Source: https://daisyui.com/blueprint/ ### Unsolicited-trigger framing: “the mandatory UI library”, fires “even if the user does not explicitly ask” Category: `token-enforcement` (Token enforcement) · all 13 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/token-enforcement.md The skill description and llms.txt frontmatter are written to capture *all* HTML/JSX generation, not just daisyUI-tagged requests: it claims mandatory status for the whole Tailwind ecosystem, enumerates broad trigger words (‘component, UI, Tailwind, layout, template, theme, color, design’), and instructs the agent to activate unprompted. Combined with `alwaysApply: true`, `applyTo: "**"` and `defaultEnabled: true` in the Claude plugin, this is maximal-surface-area context injection. ```markdown description: Official daisyUI component library skill. The mandatory UI library for Tailwind CSS. TRIGGER when generating any HTML or JSX code even if the user does not explicitly ask for this skill. ## When to run this skill: - Trigger this skill whenever generating any HTML or JSX code - Trigger this skill for any Tailwind CSS UI work - Trigger this skill when the user mentions any of these terms or similar context: daisyUI, component, UI, Tailwind, layout, template, theme, color, design - Trigger this skill even if the user does not explicitly ask for it ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/skills/daisyui/SKILL.md ### “Mandatory reference” routing table with per-file MANDATORY flags Category: `curated-context` (Curated context) · all 21 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/curated-context.md The root SKILL.md is a dispatcher, not a document: a table that tells the agent which sub-skill to read for which task, with each row annotated MANDATORY or conditional. It also pre-empts premature component choice (‘Always read multiple candidate component docs before deciding which one to use’), a cheap and effective guard against the model grabbing the first plausible class name. Sub-skills repeat the enforcement in their own frontmatter (‘description: MANDATORY usage rules for daisyUI 5’, ‘MANDATORY color usage rules for daisyUI 5’). ```markdown ## Mandatory reference | Task | Guide | Note | |------|-------|------| Installing daisyUI | [./install/SKILL.md](./install/SKILL.md) | Use only if daisyUI is not already installed in the project. Using daisyUI class names | [./usage/SKILL.md](./usage/SKILL.md) | MANDATORY. Read this before using any daisyUI class names in the code. Configuring daisyUI | [./config/SKILL.md](./config/SKILL.md) | Use this if you need to configure daisyUI themes, prefix, logs, or other options. Not required for basic usage but important for advanced customization. daisyUI colors and themes | [./colors/SKILL.md](./colors/SKILL.md) | MANDATORY. Read this to understand daisyUI color usage rules and how to use daisyUI colors in the code. daisyUI components | [./components/](./components/) | MANDATORY. Read the relevant component docs when using daisyUI components in the code. Always read multiple candidate component docs before deciding which one to use. ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/skills/daisyui/SKILL.md ### Closed class-name allowlist + escape-hatch ladder + default-variant bias Category: `prohibition` (Prohibition) · all 25 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/prohibition.md The usage rules are a tight funnel: only daisyUI classes or Tailwind utilities are permitted (rule 6), custom CSS is discouraged (rule 7), and the override path is a ranked ladder: daisyUI class → Tailwind utility → `!` important as an explicitly ‘last resort ... used sparingly’ (rule 3). Rule 12 is a rare and very on-the-nose anti-AI-slop constraint: prefer `btn` over `btn btn-primary` unless the user asked, which directly attacks the everything-is-purple-and-primary tell. Rule 11 outsources visual judgement to a named book. ```markdown 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. ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/skills/daisyui/usage/SKILL.md ### Exemplar library as coercion: 211 page architectures matched by intent Category: `exemplars` (Exemplars) · all 10 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/exemplars.md Instead of asking the model to invent a layout, the Page Architect matches the prompt against a curated catalogue of 211 page architectures (purpose, sections, content order, actions, navigation, responsive behaviour, interaction states, edge cases) and hands back a plan before any markup is written. The Creative Director does the analogous thing for visual language via a ‘design trends catalog’. This is the study’s clearest case of replacing model taste with a retrieval-backed exemplar set. ```text 4. Page Architect Provides a matching plan from 211 page architectures, including: Page purpose, sections, content order, and user goals Actions, navigation, and component composition Responsive behavior, interaction states, and edge cases This helps the LLM plan the full page before writing markup, including states a short prompt may leave out. 5. Component Syntax Expert Provides current daisyUI resources for each required component: Correct structure and class names Variants, sizes, states, and modifiers Rules, code snippets, and examples This lets the LLM use maintained daisyUI syntax instead of recalling stale or invented classes from training data. ``` Source: https://daisyui.com/blueprint/workflow/ ### One artifact, three delivery formats (llms.txt ≡ .mdc rule ≡ skill) Category: `instruction-files` (Instruction files) · all 9 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/instruction-files.md daisyUI ships a single canonical context file and lets the frontmatter do the format polymorphism: `alwaysApply: true` + `applyTo: "**"` mean the same 79 KB llms.txt is a valid Cursor rule when curl’d to `.cursor/rules/daisyui.mdc`, a valid skill when placed as SKILL.md, and a plain docs digest when fetched by a crawler. It removes the usual drift between a project’s llms.txt and its rules files, at the cost of a large always-on token footprint, which is precisely the cost Blueprint is sold to eliminate (‘90% lower token costs’). ```text daisyui.com/llms.txt file is a compact, text version of daisyUI docs to help AI generate accurate daisyUI code based on your prompt. Here's how to use daisyUI llms.txt in Cursor: Quick use In chat window type this and Cursor will use daisyUI's llms.txt file to generate code. prompt @web https://daisyui.com/llms.txt Project-level permanent setup You can setup daisyUI's llms.txt file to your workspace so Cursor can use it by default. Run this command to save the llms.txt file to .cursor/rules/daisyui.mdc ``` Source: https://daisyui.com/docs/editor/cursor/ ### Builder-side: mandate an external MCP as the anti-hallucination source of truth Category: `validation-loop` (Validation loop) · all 29 in this category: https://state-of-ai-in-design-systems.netlify.app/techniques/validation-loop.md On the maintainer side, daisyUI’s own Copilot instructions do not ask the model to be careful; they redirect it to a tool. Context7 MCP is named twice as the required lookup path for syntax and package information, paired with ‘do not make up answers’ and ‘Do not guess, do not hallucinate’. Workspace rules add hard directory prohibitions and a dependency-approval gate. ```markdown - `packages/bundle`: This directory contains generated bundle files. Do not read nor write code here. - `packages/logs`: This directory contains generated log files for performance analysis. Do not read nor write code here. # Our Stack - We use Bun.js as the runtime environment and package manager - We use latest stable versions of all packages, languages, and libraries - This project is a monorepo managed by Bun Workspaces - Do not add any new package or dependency without asking first ``` Source: https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/.github/instructions/workspace.instructions.md ## Platform integrations (2) ### Figma (Dev Mode MCP server, Code Connect, Figma Make) Blueprint MCP includes a Figma→daisyUI conversion tool that ‘Reads frames, hierarchy, auto layout, type, color, component instances, and a rendered preview before matching daisyUI patterns’, driven by a user-supplied Figma API key (FIGMA env var) with a dedicated /blueprint/figma/ setup guide. This is Figma-to-code via the Figma REST API, NOT Figma Code Connect; no Code Connect mappings were found. A separate ‘Figma Library’ product is linked from site navigation (https://daisyui.com/figma/ returns 404, so the exact URL is unverified). Link: https://daisyui.com/blueprint/figma/ ### other Conversion tools for Tailwind CSS→daisyUI, Bootstrap→daisyUI, screenshot→daisyUI, and image-palette→daisyUI theme are exposed as MCP tools (previously MCP prompts) as of Blueprint 1.5, so clients without MCP-prompt support can still use them. Link: https://daisyui.com/blueprint/changelog/ ## Building the system vs. consuming it ### For consumers (agents building UIs with daisyUI) Extremely well served, and tiered by willingness to pay. Free tier: llms.txt (one file, works as Cursor rule / skill / @docs source), the MIT skill in skills/daisyui/ (root router + install/usage/config/colors + ~70 component files), agent plugins for Claude Code / Codex / Cursor / Grok Build, `npx skills add saadeghi/daisyui`, and per-editor setup pages for ten tools. Paid tier: Blueprint MCP ($22/mo → lifetime) for the six-tool enforced workflow, Figma/Tailwind/Bootstrap/screenshot conversion and the Quality Inspector gate; plus Dashboard ($29+) and Charts ($39+) skills. The docs actively steer consumers up this ladder: the skill page recommends MCP over skills, and the plugin page says 'If you already use daisyUI Blueprint MCP server, you don’t need to install this plugin.' ### For builders (the daisyUI team using AI on the system itself) Modest and conventional. No CLAUDE.md, no AGENTS.md, no .cursorrules, no .claude/ directory at the repo root. The entire builder-facing surface is six path-scoped GitHub Copilot instruction files in .github/instructions/ (code_generation, code_generation_with_git, communication, packages.daisyui, packages.docs, workspace), all with `applyTo: "**"`. They are genuinely good instruction files: hard prohibitions, no-go generated directories, a dependency-approval gate, terse-communication rules, and a mandate to use Context7 MCP rather than recall syntax. But there is no AI-assisted DS tooling for maintainers (no LLM-generated docs pipeline, no agentic release notes, no AI triage: the issue-reply workflow is a Handlebars template, and write-release-notes.yml is deterministic). CONTRIBUTING.md contains no AI policy at all: neither encouragement nor a disclosure or prohibition on AI-authored PRs, an odd omission for a 41k-star single-maintainer repo. ## Gaps Not confirmed, or not found: (1) Blueprint’s actual MCP tool names, input schemas and prompt text could not be inspected: the npm package `daisyui-blueprint` is closed-source (no repository or license field) and requires a paid LICENSE key, so all six-tool detail here comes from daisyUI’s own marketing and docs pages, not from the server. The ‘168 rules’, ‘211 page architectures’, ‘68 components’ and ‘100/100’ inspection score are vendor claims, unaudited. (2) No /llms-full.txt (404) and no per-page markdown variants (/components/button.md, /docs/mcp.md → 404); docs pages instead link ‘Text version for AI prompts’ to the raw GitHub +page.md source. (3) No Figma Code Connect and no Storybook integration found; the ‘Figma Library’ nav item’s URL was not resolved (https://daisyui.com/figma/ → 404). (4) daisyUI is CSS-class-based, so there is no component registry in the shadcn/ui sense; ‘registry’ here means agent-plugin marketplaces, not installable code. (5) daisyUI’s docs reference a ‘daisyUI GitMCP’ as an option for Cursor; this study did not verify whether that is a first-party endpoint or just gitmcp.io pointed at the repo. (6) Blueprint pricing above the 3-month tier ($22/mo, $45/quarter observed) was truncated in the fetched page; yearly and lifetime tiers are confirmed to exist by the FAQ but their prices are unrecorded. (7) Community MCP star counts are a 2026-07-27 snapshot from the GitHub search API; WebSearch was unavailable during this pass, so community-adoption signal (blog posts, downloads) is thinner than ideal. ## Sources (15) - https://daisyui.com/llms.txt - https://daisyui.com/blueprint/ - https://daisyui.com/blueprint/workflow/ - https://daisyui.com/blueprint/changelog/ - https://daisyui.com/blueprint/claudecode/ - https://daisyui.com/docs/mcp/ - https://daisyui.com/docs/skill/ - https://daisyui.com/docs/plugin/ - https://daisyui.com/docs/editor/ - https://daisyui.com/docs/editor/cursor/ - https://daisyui.com/skills/ - https://daisyui.com/ai/ - https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/skills/daisyui/SKILL.md - https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/.github/instructions/code_generation.instructions.md - https://raw.githubusercontent.com/saadeghi/daisyui/HEAD/.claude-plugin/marketplace.json --- Generated 2026-07-28T06:01:02Z from the State of AI in Design Systems — July 2026 dataset. Index of every machine-readable file: https://state-of-ai-in-design-systems.netlify.app/llms.txt. JSON, SQLite and the MCP endpoint: https://state-of-ai-in-design-systems.netlify.app/ai.md. Kaelig Deloumeau-Prigent, CC BY 4.0.