boffin / rules
Cursor rule38 starsChanged 3 months agoMITView on GitHub
Activate ParselFire Core C++ pack index
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 4,157 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/boffin-pack-routing.mdcCursor rule
- .cursor/rules/boffin-post-change-audit.mdcCursor rule
- .cursor/rules/boffin-python-routing.mdcCursor rule
The file
We split this boffin-cpp-routing.mdc into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use its ## ROUTING and ## LEAVES records for leaf selection.
- Very specific: line 13
Use its ## STAGE-REFS records to gather the family K ids (and their mirrored X ids) at each stage of the walk.
- Distinctive: line 18
If the file is plain C, stay on universal only.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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: Activate ParselFire Core C++ pack index
globs: **/*.{cc,cpp,cxx,hh,hpp,hxx,ipp,tpp,inl}
alwaysApply: false
---
# C++ Pack Activation
For C++ source files:
- Load `packs/cpp-architecture/pack.urf.md`.
- Use its `## ROUTING` and `## LEAVES` records for leaf selection.
- Use its `## STAGE-REFS` records to gather the family K ids (and their mirrored X ids) at each stage of the walk.
For ambiguous `.h` or `.c` files that reach this rule via the always-on router:
- Apply cpp-architecture only if the file contains C++ constructs (class, template, namespace, references, std::, noexcept, overloads).
- If the file is plain C, stay on universal only.
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.