ponytail
Skill2 starsChanged 7 days agoNo licenceView 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 on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and 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, 26 of them edited; 7 of 26 edited versions we compared changed its rules; 9 new projects in the last 4 weeks, against 7 the 4 before.
How people change it
7 of 26 edited versions changed its rules, and some changes recur.
Of the 26 edited versions we compared: 19 keep every rule, 7 made changes of their own.
Rules people drop
- Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for.dropped by 5 of 7
- 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. …dropped by 3 of 7
- 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. …dropped by 2 of 7
Rules people add
- 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. …added by 3 of 7
- Never cut: validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs, anything the user asked for. User insists on the full version → build it, no re-arguing.added by 2 of 7
- Keep the structure the codebase already has: its layers, interfaces and conventions.added by 2 of 7
- Standard library or platform feature? Use it, unless the project has its own (a house component beats a native widget). On Windows + Node:
node:fs,node:path,node:testbefore a package.added by 2 of 7 - An installed dependency? Use it. Never add a dependency for a few lines.added by 2 of 7
We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.
Adopted by
Rising: 9 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.
Most recently taken up by
- gauravjuvekar/agent-skillsword for word, first seen Nov 16, 2026
- jjsizemore/jjskillstheir own version, 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/oasisword for word, first seen Nov 16, 2026
- lordm00n/skillsword for word, first seen Nov 16, 2026
Used with
Projects with it also use reimagine, herdr-cli 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
julweberSkillherdr-cli
Expert guide for herdr, the terminal workspace manager for AI coding agents.
Also in 3 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 · 20
- DietrichGebert/ponytail★ 182k100% same
- graphif/project-graph★ 4.5k100% same
- mxyhi/ok-skills★ 511100% same
- Djarvur/go-ultimate★ 31100% same
- Yassimba/loom★ 13100% same
- taljeon/plzdo★ 9100% same
- ZerroDevs/AgentsHub-Desktop★ 9100% same
- ZerroDevs/AgentsHub★ 6100% same
- FAHTHIZ/oasis★ 4100% same
- lordm00n/skills★ 4100% same
10 more not listed
Edited · 26
- superplanehq/superplane★ 10k99% same
- Cygnux-Labs/Tracekit★ 72699% same
- engasnm111/lnwjud★ 20979% same
- KrishP147/skills★ 3799% same
- nesnilnehc/ai-cortex★ 892% same
- shaderera/shaderera★ 798% same
- chrysogonus/power-agents★ 465% same
- tiagovilasboas/downshift-ai★ 498% same
- cskwork/skills★ 399% same
- oleg494/coding-kit★ 328% same
16 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.1ksame name
- TanStack/ai★ 3.4ksame name
- marmelab/atomic-crm★ 1.4ksame name
- OpenStrap/edge★ 893same 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 repository9 other files it gives its agents.
- ponytail-auditSkill
- ponytail-debtSkill
- ponytail-gainSkill
- ponytail-helpSkill
- ponytail-reviewSkill
- cloud-preflight-infra-auditorSkill
- data-lineage-upstream-validatorSkill
- hybrid-impediment-investigatorSkill
- migration-spec-refinerSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 135 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 135 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.
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.

