sipcode
CLAUDE.md46 starsChanged 31 days agoMITView on GitHub
mode: default — optimizes for: diff edits, no ceremony the rules below apply to your responses in this project. follow them. they exist so the user pays for code, not for ceremony. ### rules (default mode) 1. diff-only edits. when editing a file, output only the changed hunk plus three lines of context. never paste the full file back when three lines changed. this is the single biggest win. 2. no preamble. skip "i'll help with that", "sure", "here's what…
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 11
diff-only edits: when editing a file, output only the changed hunk plus three lines of context.
- Distinctive: line 16
no post-amble: don't summarize what was just shown unless the user explicitly asks for a summary.
- Distinctive: line 18
code over prose: when the answer is code, the code is the answer.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
<!-- sipcode:start v=2 --><!-- sipcode:block name="output-compression" mode="default" -->Sipcode Output Compression
mode: default — optimizes for: diff edits, no ceremony
the rules below apply to your responses in this project. follow them. they exist so the user pays for code, not for ceremony.
rules (default mode)
- diff-only edits. when editing a file, output only the changed hunk plus three lines of context. never paste the full file back when three lines changed. this is the single biggest win.
- no preamble. skip "i'll help with that", "sure", "here's what i did". lead with the work. the user can see what you did.
- no post-amble. don't summarize what was just shown unless the user explicitly asks for a summary.
- code over prose. when the answer is code, the code is the answer. any explanation goes after the code block, not before.
- bullets over paragraphs for any list of options, steps, or trade-offs. saves tokens versus flowing prose.
- one canonical example, not three. show one good example. skip the exhaustive variants — the user will ask if they want more.
- no filler verbs. drop "let me", "i'll go ahead and", "i'm going to". just do the thing.
(installed by sipcode. switch modes with npx sipcode rules --mode <m>.
uninstall with npx sipcode rules --uninstall.)
<!-- /sipcode:block --><!-- sipcode:end -->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.