Cursor plus brand guidelines: one workflow
Keep agents and humans aligned on colors, voice, and tokens while you ship features.
Cursor is fast. It is also eager to invent colors that never existed in your palette. The fix is not "prompt harder." It is giving the agent the same brand artifacts your team uses.
Put guidelines where agents read
Export design.md and tokens into the repo root or a brand/ folder. Point Cursor rules at that path. When the agent suggests UI, it should cite your variables, not random hex values.
Short rules beat long manifestos
Three rules work well:
- Use CSS variables from design.md for all colors and fonts
- Match voice: direct, founder-to-founder, no hype adjectives
- Link to docs for product facts instead of guessing
Sync after brand changes
When you rerun brand flow and update tokens, commit in one PR. Agents pick up changes on next session. Splitting brand and code across weeks reintroduces drift.
Read the Cursor integration doc for MCP setup. Combine with export and use in code so generated components stay on-system.
Review like any other PR
Treat agent output as a junior contributor. Visual check against guidelines, run lint, ship. Speed without review is how you get seventeen shades of blue.
Close the loop with blog and docs
When you publish a feature post, link to the doc page that explains it. Search engines and users both benefit from tight internal links between blog, docs, and app.