Why Cursor and Claude need a brand kit

Cursor and Claude Code generate UI fast — but without design constraints, every prompt produces different fonts and hex codes. An AI brand kit for Cursor and Claude gives agents a single source of truth: headline font, body font, primary color, accent, surfaces, and usage rules in a file they read automatically.

AI Brand Kits generates complete kits and exports DESIGN.md to your repo root. Tell Cursor or Claude Code to follow DESIGN.md, paste the auto-generated prompt, and every component stays on-brand.

What to include in a Cursor / Claude brand kit

Both agents index project markdown and respect explicit design instructions when you provide structured tokens instead of vague descriptions.

• DESIGN.md with fonts, colors, spacing, and component rules
• Semantic tokens — primary, accent, surface, muted — not raw hex lists
• Tailwind config snippet and CSS variables ready to paste
• Auto-generated prompt tuned for Cursor and Claude Code
• tokens.json for programmatic access in your codebase

Set up a brand kit for Cursor or Claude Code

Generate your kit below, export DESIGN.md, and add it to your project. Reference it in AGENTS.md or your system prompt for best results.

• Randomize or pick font pairs and color palettes
• Customize tokens until the live preview looks right
• Download DESIGN.md and place it in your repo root
• Paste the AI prompt and tell your agent to follow DESIGN.md

Cursor vs Claude Code brand workflows

Cursor users often drop DESIGN.md alongside .cursorrules or AGENTS.md. Claude Code users add it to the project root where Claude indexes context files. Both approaches work — the key is giving agents named tokens and explicit font roles.

Regenerate kits anytime your brand evolves. Re-export and your agent picks up the latest tokens.

Frequently asked questions