Skip to main contentSkip to footer
← For agents
For agents

Cursor

Add the Blueprint .mdc rules file to your Cursor setup for always-on doctrine guidance.

Download agent assets

Install the rule

Download blueprint-core.mdc from the agent assets page. Save it to .cursor/rules/blueprint-core.mdc in your repository. Cursor picks it up automatically — no restart required. The rule activates on every session in that project directory.

What it enforces

The rule file carries the eight Always Do directives: keep agent boundaries explicit, prefer prepare/propose/draft before execute, use human approval for risky or irreversible actions, show progress and runtime state, design fallback paths, preserve reversibility, prefer structured outputs, and optimise for production usage not demo behavior.

Optional MCP layer

Add the Blueprint MCP server in Cursor settings for live doctrine retrieval during sessions. The rule file works without MCP — MCP adds the ability to fetch specific examples and principles on demand during a conversation.

CursorCursor
Persistent rules + live MCP
Use the `.mdc` file for always-on editor guidance and the MCP endpoint for live principle, cluster, and example lookups.

Rule path

.cursor/rules/blueprint-doctrine.mdc
Cursor Rules Exportllms.txt

Kickoff prompt

Always apply the blueprint doctrine. Clarify the relevant principle or cluster first, then use the live MCP to search examples and verify runtime, steering, or approval-boundary patterns.

Also in this section

CodexClaude CodeMCP setup