antistrefo / rules
Cursor rule4 starsChanged 9 days agoMITView on GitHub
Four-line file banner and the single pragma once
We split this banner.mdc into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Every file opens with exactly four comment lines.
- Distinctive: line 22
Keep each banner line under 100 columns.
≈ “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: Four-line file banner and the single pragma once
alwaysApply: true
---
# Banner
Every file opens with exactly four comment lines. C uses `//`. Scripts and text use `#`. A `.py` shebang may occupy line 1; the banner then starts on line 2. `CMakePresets.json` and `LICENSE` have no banner.
// re_arena.h - bump allocator giving one malloc and one free per command.
// Module: util (C11).
// Owns: bump-pointer blocks, chunk list, reset and free.
// Depends: none. No I/O, no globals, thread-unsafe by design.
Slots, in order:
1. Basename, then one-line purpose. The gate requires the filename on this line.
2. `Module: <name> (<language>).` including the period.
3. `Owns: ...`
4. `Depends: ...` and the architectural constraint on the same line.
Keep each banner line under 100 columns. clang-format wraps a long line 3 or 4 onto line 5, and rule 2 then fails.
`#pragma once` follows the banner in every header, exactly once.
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/build.mdcCursor rule
- .cursor/rules/gate.mdcCursor rule
- .cursor/rules/layout.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.