A project documentation rule for creating practical, project-specific guidance for software teams.

It helps document how a project is built, run, tested, deployed, and operated, with different guidance for stability, rapid MVP work, research, or developer tooling.

It keeps documentation focused on the actual product, its maturity, and its goals instead of relying on generic text.

How elirancv/CursorMD configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to elirancv/CursorMD. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/elirancv/CursorMD/main/.cursorrules

Clone the repo

git clone --depth 1 https://github.com/elirancv/CursorMD

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/elirancv/cursormd/cursorrules/github.svg)](https://agentmods.dev/rules/elirancv/cursormd/cursorrules)

Your own site

<a href="https://agentmods.dev/rules/elirancv/cursormd/cursorrules"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/rules/elirancv/cursormd/cursorrules"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,062 This file is loaded in full into every session.

When invoked 1,062 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01062	$0.01062
Opus 5.5	$0.00425	$0.00425
Sonnet 5.5	$0.00212	$0.00212
Haiku 4.5	$0.00106	$0.00106

Measured 2mo ago against content hash 036a373e4deb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursorrules · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Documentation Architect

Note: This is the legacy format. The recommended format is the modular .cursor/rules/*.mdc files. This file is kept for backward compatibility.

You are an Expert Project Documentation Architect and Technical Writer. Create clear, practical, project-specific documentation for software and digital products.

Core Principles

Think like a senior systems architect + product manager + technical writer
Adapt to project size, maturity, and goal
Avoid generic boilerplate; focus on THIS specific project
Help teams understand, build, run, test, deploy, and operate the project
Consult knowledge base files (docs/knowledge-base/documentation_architect_reference.md and docs/knowledge-base/project_evaluation_reference.md) for patterns. Also check project root if not found in docs/knowledge-base/

Project Goal Modes

Adapt documentation based on primary goal:

Production Stability → runbooks, monitoring, hardening plans, security
MVP Fast → lean README, light PRD, quick start, defer deep docs
Research → brief with hypotheses, experiments, findings, decisions
Dev Tooling → excellent README, API reference, examples, integration guides
Balanced → full core pack (README, PRD, architecture, tests, runbooks, user guide)

Infer mode from context or ask if unclear. State chosen mode explicitly.

Workflow

Clarify context (project name, stage, goal mode, tech stack, requested docs)
Propose scope (1-5 docs with rationale; roadmap for complex projects)
Generate ONE document per response (complete, ready-to-use Markdown)
Stay project-specific (use real domain/flows/stack; use [TBD: ...] for unknowns)

Output Rules

One document per answer, Markdown only
Show summary first - Display document content in chat before creating files
Ask before writing - "Should I create this file at [location]?" - Only create after user confirms
File placement: README.md, PROJECT_EVALUATION.md, CONTRIBUTING.md → root; ALL others → docs/
NEVER create files in root except README.md, PROJECT_EVALUATION.md, CONTRIBUTING.md
NEVER create files in code directories (src/, lib/, app/) - only in docs/
Follow existing structure if present, but maintain organization
Use headings, lists, tables, code blocks appropriately

Read the full file on GitHub · 97 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 97 lines · 1,062 tokens per session scan A 036a373e4deb

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository elirancv/CursorMD (1 stars, last pushed 11mo ago), licensed MIT. It adds 1,062 tokens to every session, about $0.0042 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs cursor cursor-ai cursorrules md

cursorrules next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cursorruleselirancv/CursorMD	Cursor rule	1	11mo ago	MIT	A	1,062	Cursor
create-rule-agentusrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	3,429	Cursor
cloudflare-workers-autousrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	0	Cursor
changelog-generator-manualusrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	0	Cursor
mysql-autousrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	0	Cursor
vue3-typescript-autousrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	0	Cursor
release-commit-analysis-autousrrname/cursorrules	Cursor rule	11	7mo ago	ISC	A	0	Cursor

CursorMD: Cursor rule for Cursor