octo-cluster
CLAUDE.md3 starsChanged 23 days agoMITView on GitHub
Same harness as Cursor. Always-on rules are the Cursor rule files, imported below (single source of truth). Contract and commands: AGENTS.md (read on demand, not imported). @.cursor/rules/00-consumer-boundary.mdc @.cursor/rules/execute-operator-intent.mdc @.cursor/rules/ponytail-lite.mdc @.cursor/rules/caveman-mode.mdc @.cursor/rules/cost-routing.mdc
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-consumer-boundary.mdcCursor rule
- .cursor/rules/caveman-mode.mdcCursor rule
- .cursor/rules/cost-routing.mdcCursor rule
- .cursor/rules/execute-operator-intent.mdcCursor rule
- .cursor/rules/ponytail-lite.mdcCursor rule
- debugSkill
- ponytail-liteSkill
- promptSkill
- pr-reviewSkill
- shipSkill
- systematic-debuggingSkill
The file
We split this CLAUDE.md 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
Use from any other folder: install the plugin (claude plugin install octo-cluster --marketplace renanflustosa/octo-cluster).
≈ “Common” is an estimate: at least 1 in 5 of the 28,029 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
Claude Code entry - octo-cluster
Same harness as Cursor. Always-on rules are the Cursor rule files, imported below (single source of truth). Contract and commands: AGENTS.md (read on demand, not imported).
@.cursor/rules/00-consumer-boundary.mdc @.cursor/rules/execute-operator-intent.mdc @.cursor/rules/ponytail-lite.mdc @.cursor/rules/caveman-mode.mdc @.cursor/rules/cost-routing.mdc
Claude Code notes
- Skills live in
.claude/skills/(Cursor loads the same folder). Slash:/prompt,/ship,/debug; auto:ponytail-lite,systematic-debugging,pr-review. - Local diffs: prefer the built-in
/code-review; GitHub PRs:pr-review. - Use from any other folder: install the plugin (
claude plugin install octo-cluster --marketplace renanflustosa/octo-cluster). Manifests:.claude-plugin/; always-on context:hooks/hooks.json(SessionStart injectsponytail-lite+cost-routing; Bash/Edit hooks feedscripts/lessons.ps1, test withpwsh -File scripts/lessons.test.ps1). Check withclaude plugin validate ..
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.

