One brand kit for Cursor and Claude Code
Cursor and Claude Code are the default UI engines for modern product teams. Both read markdown context, both respond to structured tokens, and both drift without constraints. An AI brand kit for Cursor and Claude gives every session the same headline font, body font, primary color, accent, surfaces, and usage rules.
AI Brand Kits generates complete kits and exports DESIGN.md to your repo root. Tell Cursor or Claude to follow DESIGN.md, paste the auto-generated prompt, and every component stays on-brand. The same export powers v0 and Lovable when your team splits work across tools.
For Claude-specific setup, see brand kit for Claude Code. For Cursor rules, see how to make Cursor follow my brand.
What to include in a Cursor and 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 in prompts
- Tailwind config snippet and CSS variables ready to paste
- Auto-generated prompt tuned for Cursor and Claude Code (Claude design system prompt)
- tokens.json for programmatic access in your codebase
- AGENTS.md and .cursorrules guidance for persistent enforcement
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 in the playground until 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
- Export Pro zip from Export for AI Agents for tokens.json and globals.css
Cursor vs Claude Code brand workflows
Cursor users 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 when you give agents named tokens and explicit font roles.
Regenerate kits anytime your brand evolves. Re-export and your agent picks up the latest tokens. Save versions in your dashboard for team access.
- Solo devs switching between Cursor and Claude Code on one repo
- Teams using Cursor for app code and Claude Code for scripts and migrations
- Agencies handing clients AI ready brand guidelines both tools read
FAQ
- Where should I put DESIGN.md for Cursor?
- Place DESIGN.md in your repository root. Cursor indexes root-level markdown. Reference it in AGENTS.md or your prompt: "Follow DESIGN.md for all UI decisions."
- Does Claude Code read DESIGN.md automatically?
- Claude Code indexes project files including markdown in the repo root. Explicitly mention DESIGN.md in your instructions. See DESIGN.md Claude prompt.
- Can I use the same brand kit in both Cursor and Claude?
- Yes. DESIGN.md is agent-agnostic. Export once and use it across Cursor, Claude Code, v0, and Lovable.
- What if my UI still looks inconsistent?
- Add cursor rules for design tokens, import tokens.json in theme code, and read consistent UI with AI coding.
- Is export free?
- DESIGN.md download and prompt copy are free. Full zip with tokens.json and Tailwind is on Pro.
Related
Free tools
Interactive utilities you can use without an account. Each tool links to related guides and export workflows across the site.