ponytail-lite
Skill3 starsChanged 23 days agoMITView on GitHub
Minimal implementation ladder before writing code. Apply before each edit; question over-scope during planning. Complements caveman (prose). Inspired by DietrichGebert/ponytail (MIT).
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Moozy23232/skillstheir own version, first seen Jul 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Moozy23232/skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
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
- .cursor/rules/ponytail-lite.mdcCursor rule
- debugSkill
- promptSkill
- pr-reviewSkill
- shipSkill
- systematic-debuggingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 14
Before writing any code, stop at the first rung that holds:
- Distinctive: line 24
Order: read and trace the real flow first, then climb.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill 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
Ponytail-lite — minimal implementation
Adapted from DietrichGebert/ponytail (MIT).
Lazy means efficient, not careless. Complements caveman-mode rule (shorter replies). This skill governs what to implement, not how to phrase status updates.
The ladder
Before writing any code, stop at the first rung that holds:
- YAGNI — Does this need to be built at all?
- Reuse — Does it already exist in this codebase? Reuse the helper, util, or pattern — do not rewrite.
- Stdlib — Does the standard library already do this?
- Native — Does a native platform feature cover it? (
<input type="date">,Intl,path.Join, etc.) - Installed dep — Does an already-installed dependency solve it?
- One line — Can this be one line? Make it one line.
- Minimum — Only then: write the minimum code that works.
Order: read and trace the real flow first, then climb. Lazy about the solution, never about reading.
Examples by rung
| Rung | Bad | Good |
| YAGNI | Build a generic plugin system for one hook | Inline the one hook |
| Reuse | New parseDate() when utils/date.ts exists | Import existing helper |
| Stdlib | Hand-rolled email regex class | "@" in email or stdlib validator |
| Native | flatpickr for a date field | <input type="date"> |
| Installed dep | Add lodash for one groupBy | Use existing dep or stdlib |
| One line | 15-line wrapper around dict(zip(...)) | dict(zip(keys, values)) |
| Minimum | Framework for a one-off script | Direct script |
Bug fix = root cause
A report names a symptom. Grep every caller of the function you touch and fix the shared function once — one guard there beats one patch per caller.
Carve-outs (never cut)
- Understanding the problem (read fully, trace flow before picking a rung)
- Input validation at trust boundaries
- Error handling that prevents data loss
- Security, accessibility
- Hardware calibration (clocks drift, sensors read off)
- Anything explicitly requested by the user or ticket
Non-trivial logic leaves ONE runnable check (assert-based self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test.
Debt comments
Mark intentional simplifications:
# ponytail: global lock; upgrade to per-key sharding if contention shows upNames the ceiling and the upgrade path so "later" does not become "never".
Phase integration
| Phase | Behavior |
| Plan | Rejected alternatives cite rung; plan must not violate carve-outs |
| Execute | Ladder active before each file edit |
/ship | Prefer smallest diff that passes the boundary gate |
Does NOT replace
- caveman-mode rule — prose compression on status turns
- systematic-debugging — reproduce before fix; ponytail-lite applies after root cause is understood
Trigger: active when .cursor/rules/ponytail-lite.mdc applies (Cursor rule; imported by CLAUDE.md in Claude Code).
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.

