antistrefo / rules
Cursor rule4 starsChanged 9 days agoMITView on GitHub
C11 core versus C++ shell, bounded reads, and the command table
We split this architecture.mdc into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 10
Every byte of file data is read through re_read / re_rd*, which return failure or zero past the end.
- Very specific: line 16
No Boost, no nlohmann/json, no other third-party C++ library.
≈ “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: C11 core versus C++ shell, bounded reads, and the command table
alwaysApply: true
---
# Architecture
`src/utils` and `src/features` are C11 with `extern "C"` headers, no exceptions, no RTTI. `src/cli` and `src/mcp` are C++17 and never reinterpret binary data themselves. They call `re_*` and render.
Every byte of file data is read through `re_read` / `re_rd*`, which return failure or zero past the end. No raw pointer arithmetic into file data. Map the file with `CreateFileMapping` / `MapViewOfFile` (`mmap` under `#ifdef` for POSIX). Do not slurp the whole file.
One command table of `{name, summary, args, entry, schema}` drives both argv parsing and MCP `tools/list`. Do not add a command on only one surface.
Heavy dependencies sit behind an opaque vtable. `re_disasm` is that seam. Feature code never names a Capstone type. `RE_ENABLE_DISASM=OFF` drops the table. The built backend is the self-contained x86-64 decoder in `src/features/disasm/`.
No Boost, no nlohmann/json, no other third-party C++ library. `re_jw` is the JSON emitter for the whole project.
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/banner.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.