OpenCRE / rules
Cursor rule199 starsChanged 5 months agoCC0-1.0View on GitHub
Verify or ask — no guessing packages, APIs, patterns, or incomplete code
We split this never-assume.mdc into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Do not add markdown/docs files the user did not ask for.
- Distinctive: line 24
Do not use "made with cursor" or similar in commits.
- Distinctive: line 29
Use Makefile targets over ad-hoc commands when available.
- Very specific: line 30
Prefer scripts/db/ for production DB operations over raw SQL.
≈ “Common” is an estimate: at least 1 in 5 of the 6,350 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
--- description: Verify or ask — no guessing packages, APIs, patterns, or incomplete code alwaysApply: true --- # Never Assume | Do NOT | Instead | |--------|---------| | Assume package names, API endpoints, DB schema, or file locations | Read the codebase; grep; ask | | Add new dependencies without explanation | State why, alternatives considered, and get approval | | Use mocks unless explicitly requested | Prefer integration-style tests matching `@application/tests/` patterns | | Replace code with placeholders, TODOs, or stubs | Ship complete, working code | | Write incomplete implementations | Finish the feature or stop and explain what's blocked | | Guess production/staging targets for DB ops | Confirm target app; follow `production-db-ops-safety.mdc` | | Commit or push unless asked | Wait for explicit user request | ## Scope and diff discipline - Minimize scope — smallest correct diff; no drive-by refactors. - Match surrounding naming, types, imports, and documentation level. - Comments only for non-obvious business logic. - Do not add markdown/docs files the user did not ask for. - Do not use "made with cursor" or similar in commits. ## OpenCRE conventions - Mirror patterns in existing code (importers, tests, web routes). - Use Makefile targets over ad-hoc commands when available. - Prefer `scripts/db/` for production DB operations over raw SQL.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 3,978 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/alembic-deploy-guardrail.mdcCursor rule
- .cursor/rules/autonomous-workflow.mdcCursor rule
- .cursor/rules/complete-ticket.mdcCursor rule
- .cursor/rules/context-management.mdcCursor rule
- .cursor/rules/multi-agent-workflow.mdcCursor rule
- .cursor/rules/plan-first-workflow.mdcCursor rule
- .cursor/rules/production-db-ops-safety.mdcCursor rule
- .cursor/rules/requirements-gate.mdcCursor rule
- .cursor/rules/tdd-workflow.mdcCursor rule
- .cursor/rules/verifiable-goals.mdcCursor rule
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.