antistrefo / rules
Cursor rule4 starsChanged 9 days agoMITView on GitHub
JSON stdout contract, stderr diagnostics, and error codes
We split this output.mdc into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Every response carries "schema":"antistrefo/1".
≈ “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: JSON stdout contract, stderr diagnostics, and error codes
alwaysApply: true
---
# Output contract
stdout carries exactly one JSON object plus `\n`. Nothing else. In `mcp` mode, stdout is only newline-delimited JSON-RPC frames.
stderr carries diagnostics. `re_log_*` is the only writer. It is silent in mcp mode and when `RE_LOG=0`.
Errors in JSON mode go to stderr and use a nonzero exit:
{"schema":"antistrefo/1","error":{"code":1,"message":"..."}}
Every response carries `"schema":"antistrefo/1"`. Collections carry `count` and `truncated` and accept `--offset` / `--limit`. Default limit is 200.
| Code | Meaning |
|---|---|
| 0 | ok |
| 1 | internal error, the fallback when no specific code applies |
| 2 | usage error |
| 3 | not a recognized binary |
| 4 | malformed binary, or a read that ran past the end |
| 5 | unsupported format or architecture |
| 6 | I/O error or out of memory |
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/layout.mdcCursor rule
- .cursor/rules/no-personal-emails.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.
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.