Using with Cursor

Cursor uses an indexed view of your repo when generating code. DESIGN.md is part of that index — no plugin, no setting, no MCP server.

Install

designdrop add stripe

That's the install. Cursor's next AI Chat / cmd+k invocation has access to the file.

Anchor the agent

In a fresh chat:

Reference DESIGN.md when building UI in this repo. Quote the relevant token
sections before generating each component.

Cursor's agent will then ground generations in the file. The "quote it back" instruction matters — it forces the model to ground in actual file content rather than its training prior.

Per-rule anchoring

For repos that use Cursor Rules (.cursor/rules/), add a small rule that points the agent at the file:

---
description: Apply when generating UI components
globs: ["apps/**/*.tsx", "src/**/*.tsx"]
alwaysApply: false
---
 
When generating UI, follow apps/web/DESIGN.md. Quote the relevant token
sections (Colors, Typography, Patterns) in your response before writing
component code.

This ensures the design grounding kicks in for every UI-touching prompt without you having to repeat it.

Multi-DESIGN.md repos

If you have separate DESIGN.md files for sub-apps (marketing site vs. authenticated dashboard), use globs in your Cursor Rules to pick the right one:

---
description: Marketing UI follows the public design system
globs: ["apps/web/**/*.tsx"]
---
 
Follow apps/web/DESIGN.md for marketing components.

---
description: App UI follows the dashboard design system
globs: ["apps/app/**/*.tsx"]
---
 
Follow apps/app/DESIGN.md for authenticated components.