antistrefo / rules
Cursor rule4 starsChanged 9 days agoMITView on GitHub
Source tree, include paths, folder cap, and how tests must assert
We split this layout.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Never generalise from one sample.
≈ “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: Source tree, include paths, folder cap, and how tests must assert alwaysApply: true --- # Layout Include root is `src/`. Use `#include "utils/mem/re_arena.h"` and `#include "features/pe/re_pe.h"`. - `src/utils/<cat>/` shared utilities: text, mem, algo, sys, json, tui - `src/features/<cat>/` one directory per analysis area - `src/cli/` argv dispatch and rendering. `src/mcp/` MCP stdio server - `tests/` CTest targets. `docs/util-catalog.md` is the util lookup; read it before new code - `Tools/` is reserved and not ours A folder under `src/` with more than 15 files must be split by category. The gate fails the build. Never generalise from one sample. Coverage, matching, performance, and robustness claims are checked against all five corpus files before they are reported. A test asserts content, not only counts. Where the correct value is knowable, pin it. Where a bug can be reintroduced to prove the test catches it, do that before trusting the test.
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 repository9 other files it gives its agents.
- .cursor/rules/architecture.mdcCursor rule
- .cursor/rules/banner.mdcCursor rule
- .cursor/rules/build.mdcCursor rule
- .cursor/rules/gate.mdcCursor rule
- .cursor/rules/no-personal-emails.mdcCursor rule
- .cursor/rules/output.mdcCursor rule
- .cursor/rules/project.mdcCursor rule
- .cursor/rules/reuse.mdcCursor rule
- .cursor/rules/scope.mdcCursor rule
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.