octo-cluster / rules
Cursor rule3 starsChanged 23 days agoMITView on GitHub
Ponytail-lite — minimal implementation ladder before writing code
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.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
- debugSkill
- ponytail-liteSkill
- promptSkill
- pr-reviewSkill
- shipSkill
- systematic-debuggingSkill
The file
Files
--- description: Ponytail-lite — minimal implementation ladder before writing code alwaysApply: true --- # Ponytail-lite (lazy senior dev mode) Lazy means efficient, not careless. Climb the ladder only after reading the real flow. YAGNI → reuse → stdlib → native → installed dep → one line → minimum code. Bug fix = root cause once. No unrequested abstractions. Deletion over addition. Skill: `.claude/skills/ponytail-lite/SKILL.md`
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.

