Design UI with Claude Code using daisyUI skill or Blueprint MCP for component-aware Tailwind CSS generation.
To design UI with Claude Code, give Claude a screen goal and a component system. Do not ask for a vague "clean page" and expect consistent design decisions.
Name the page, the user goal, and the states. For example: billing settings with current plan, invoice list, failed payment alert, and cancellation flow.
For free static guidance, install the skill:
npx skills add saadeghi/daisyui --agent claude-code --yesFor on-demand component context, install Blueprint MCP:
claude mcp add daisyui-blueprint --env LICENSE=YOUR_LICENSE_KEY --env EMAIL=YOUR_EMAIL --env FIGMA=YOUR_FIGMA_API_KEY -- npx -y daisyui-blueprint@latestFIGMA is optional unless you need Figma-to-code conversion.
Design a customer support inbox with daisyUI skill. Use a drawer for navigation, cards for conversation previews, badges for priority, and a modal for assigning a ticket.Read daisyUI skill for Claude Code and daisyUI MCP for Claude Code.
After Claude Code writes the UI, check whether repeated parts use daisyUI classes. If a screen has custom utility-only buttons next to daisyUI buttons, ask Claude to normalize the actions. If it hardcodes colors, ask it to use daisyUI semantic colors.
This review loop is short, but it matters. It turns the first generated draft into a reusable pattern for the next Claude Code edit.
Used by engineers at