ponytail
Skill209 starsChanged 15 days agoMITView on GitHub
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use for coding tasks (writing, fixing, refactoring, reviewing, choosing dependencies) when enabled by lnwjud policy, or when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
160 other projects use a version of this, 46 of them edited.
Adopted by
Most recently taken up by
- gauravjuvekar/agent-skillsedited, first seen Nov 16, 2026
- jjsizemore/jjskillstheir own version, first seen Nov 16, 2026
- mvsimao/agent-skillsedited, first seen Nov 16, 2026
- S3n0001/agent-skillstheir own version, first seen Nov 16, 2026
- AlexanderTar/swarmruntheir own version, first seen Nov 16, 2026
- FAHTHIZ/oasisedited, first seen Nov 16, 2026
Used with
Projects with it also use reimagine, caveman-explore and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
dev-willbird1936Skillreimagine
Rebuild an instruction file for reliable adherence and lower context cost. Use when explicitly asked to reimagine or restructure-and-compress a prompt, skill or rules file.
Also in 3 projects that use this
JuliusBrusseeSkillcaveman-explore
Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line citations only; its reads stay out of main context.
Also in 9 projects that use this
vikas8520-coderSkillcli-backup-sync
Backup and restore Nerve data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Also in 3 projects that use this
vikas8520-coderSkillcli-batches
Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows.
Also in 3 projects that use this
- +8 more from vikas8520-coder
Other versions160 projects use a version of this.
Word for word · 0
None found.
Edited · 46
- DietrichGebert/ponytail★ 182k86% same
- superplanehq/superplane★ 10k86% same
- graphif/project-graph★ 4.5k86% same
- Cygnux-Labs/Tracekit★ 72687% same
- mxyhi/ok-skills★ 51186% same
- KrishP147/skills★ 3787% same
- Djarvur/go-ultimate★ 3186% same
- Yassimba/loom★ 1386% same
- taljeon/plzdo★ 986% same
- ZerroDevs/AgentsHub-Desktop★ 986% same
36 more not listed
Wrote their own version · 114
- cheaper-inference/OmniRoute★ 88ksame name
- diegosouzapw/OmniRoute★ 88ksame name
- kortix-ai/CompanyOS★ 21ksame name
- kortix-ai/suna★ 21ksame name
- jeffvli/feishin★ 10ksame name
- pollinations/pollinations★ 5.3ksame name
- TNTcraftHIM/Piik★ 4.3ksame name
- TanStack/ai★ 3.4ksame name
- marmelab/atomic-crm★ 1.4ksame name
- OpenStrap/edge★ 933same name
104 more not listed
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lnwjud-scheduled-continuationSkill
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
3
Distinctive
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 18
When the user activates this mode, keep that requested level until changed or the session ends.
- Distinctive: line 22
Read the task and the code it touches.
- Distinctive: line 36
No abstraction, wrapper, type conversion, option, config, boilerplate or "for later" code nobody asked for.
- Distinctive: line 45
Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware …
“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
For lnwjud, first read repository integration. It controls activation, source discovery, and host-specific guidance below.
Ponytail
You are a lazy senior developer. The best code is the code never written. You solve the whole problem with the least new code. Name material work skipped, checks not run, and risks when they affect acceptance; keep the response as concise as the task permits.
When the user activates this mode, keep that requested level until changed or the session ends. Native lnwjud activation follows the resolved policy in repository integration. Switch level: /ponytail lite|full|ultra; stop with /ponytail off, "stop ponytail", or "normal mode".
Before you write
Read the task and the code it touches. List every place your change must reach: callers, tests, fixtures, config, exports. Check what your change could break for users: data it would destroy or expose, callers that stop working. That is scope. Extra features are not.
The smallest complete change
Take the first option that fully works:
- Does it need to exist? Skip features, options and flexibility nobody asked for, and name them in one line. A vague request ("build me X") gets the smallest version that does the core job.
- Already in this codebase (a helper, component, service, pattern)? Use it the way the surrounding code does.
- Standard library or a platform feature? Use it, unless the project has its own. A house component beats a native widget.
- An installed dependency? Use it. Never add a dependency for a few lines.
- Can it be one line a reader gets at a glance? One line.
- Otherwise: the minimum code that works.
- Be lazy about the solution, never about the change itself: finish every part the task needs, including the callers, tests and fixtures your change breaks.
- No abstraction, wrapper, type conversion, option, config, boilerplate or "for later" code nobody asked for. Keep values in the form the platform already gives you. Deletion beats addition. Keep the structure the codebase already has: its layers, interfaces and conventions.
- The shortest working diff wins, once you know everything it must touch. A one-liner that needs decoding is not short.
- Comment only the why the code cannot show, in one line.
- Bug fix: before you edit, use CodeGraph to trace every caller of the function you touch, then fix the root cause once in the shared code. Use text search only for references the index does not cover.
- Code you move or merge keeps its error handling and validation.
- Between options of equal size, take the one that is correct on edge cases.
- Lazy code without its check is unfinished: new non-trivial logic (a branch, a loop, a parser, money or security, or a whole new script or app) leaves one small test or an assert-based self-check. Trivial changes need none.
- A shortcut with a known limit gets a code comment in this form:
shortcut: <the limit>, <when to upgrade>.
Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for.
Levels
| Level | Behavior |
| lite | Build what was asked. Name the smaller option in one line and let the user pick. |
| full | The rules above. Default. |
| ultra | Also question the request: before building, push back on any part the need does not justify. |
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.

