ponytail-debt
Skill0 starsChanged 20 days agoMITView on GitHub
List every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.
62 other projects use a version of this, 51 of them edited; 38 of 51 edited versions we compared changed its rules; 6 new projects in the last 4 weeks, against 7 the 4 before.
How people change it
38 of 51 edited versions changed its rules.
Of the 51 edited versions we compared: 9 keep every rule, 4 are an older text, 38 made changes of their own.
Not in older versions
- If the user names their own marker word (
/ponytail-debt TODO), grep for that word instead.missing from 4 of 4
Rules people drop
- If the user names their own marker word (
/ponytail-debt TODO), grep for that word instead.dropped by 38 of 38
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
Steady: 6 new projects took it in the last 4 weeks, 0.9× the 4 weeks before.thin data
Most recently taken up by
- ezmichaely/make-it-ezyword for word, first seen Nov 15, 2026
- gladosAagman/ponytailedited, first seen Nov 15, 2026
- GabrieleDattile/agent-superpowersedited, first seen Nov 15, 2026
- Binbin-miao/workbuddy-expert-teamtheir own version, first seen Nov 15, 2026
- mintunitish/tandemedited, first seen Nov 15, 2026
- ZerroDevs/AgentsHub-Desktopword for word, first seen Nov 15, 2026
Used with
Projects with it also use caveman-help, caveman-commit and 6 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.
huangzidaSkillcaveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
Also in 5 projects that use this
huangzidaSkillcaveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Also in 6 projects that use this
JuliusBrusseeSkillcaveman-stats
Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.
Also in 4 projects that use this
JuliusBrusseeSkillcavecrew
When to delegate to `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit) or `cavecrew-reviewer` (diff review) instead of working inline or using `Explore`. Their output is compressed, so main context lasts longer.
Also in 4 projects that use this
MicrosoftSkillimpeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.
Also in 8 projects that use this
AnasX7Skillimagegen-frontend-mobile
Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.
Also in 3 projects that use this
- +1 more from huangzida
Other versions62 projects use a version of this.
Word for word · 7
- DietrichGebert/ponytail★ 182k100% same
- ZerroDevs/AgentsHub-Desktop★ 9100% same
- ZerroDevs/AgentsHub★ 6100% same
- Eclipter/agents★ 1100% same
- ezmichaely/make-it-ezy★ 0100% same
- Hiraeth-Wave/Skills★ 0100% same
- vinhmone/real-skills-for-dev★ 0100% same
Edited · 51
- kortix-ai/CompanyOS★ 21k59% same
- kortix-ai/suna★ 21k59% same
- marmelab/atomic-crm★ 1.4k59% same
- Cygnux-Labs/Tracekit★ 72688% same
- mezotv/notra★ 25659% same
- usenotra/notra★ 25659% same
- engasnm111/lnwjud★ 20960% same
- jacred-fdb/jacred★ 13959% same
- Wenaixi/dsh-ponytail★ 4659% same
- KenSuh/open-agent-harness★ 3359% same
41 more not listed
Wrote their own version · 4
- dekoza/oh-my-slop★ 4same name
- Binbin-miao/workbuddy-expert-team★ 1same name
- raditia/CraftKit★ 1same name
- lost-rob0t/skills★ 0same 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 repository86 other files it gives its agents.
- ai-assistant-editor-setupSkill
- api-and-interface-designSkill
- banner-designSkill
- brainstormingSkill
- caveman-exploreSkill
- caveman-reviewSkill
- chat-silence-diagnosisSkill
- ci-cd-and-automationSkill
- code-auditSkill
- codebase-designSkill
- koordinator-team-dispatchSkill
- constraint-driven-developmentSkill
- context-engineeringSkill
- cpanel-shared-hosting-deploySkill
- cross-profile-cron-opsSkill
- deprecation-and-migrationSkill
- documentation-and-adrsSkill
- domain-modelingSkill
- doubt-driven-developmentSkill
- finishing-a-development-branchSkill
- frontend-designSkill
- git-workflow-and-versioningSkill
- graphic-design-laneSkill
- hermes-gateway-web-uiSkill
- hermes-profile-hygieneSkill
- hermes-profile-provisioningSkill
- hermes-service-persistenceSkill
- hermes-stream-stale-diagnosisSkill
- hermes-team-dashboardSkill
- idea-refineSkill
- incremental-implementationSkill
- indonesian-official-lettersSkill
- internal-commsSkill
- interview-meSkill
- investigate-firstSkill
- kanban-rate-limit-resilienceSkill
- karpathy-guidelinesSkill
- large-project-gated-deliverySkill
- lean-buildSkill
- live-agent-office-operationsSkill
- live-react-runtime-qaSkill
- live-web-release-verificationSkill
- markdown-pdf-pipelineSkill
- marketing-strategySkill
- meta-social-publishingSkill
- meta-threads-oauth-lifecycleSkill
- migrationSkill
- multi-profile-project-orchestrationSkill
- network-operationsSkill
- observability-and-instrumentationSkill
- office-skill-distributionSkill
- organization-site-menu-researchSkill
- performance-optimizationSkill
- php-upload-size-limitsSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- ponytailSkill
- portable-app-handoffSkill
- receiving-code-reviewSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 54 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Every deliberate ponytail shortcut is marked with a shortcut: comment naming its ceiling and upgrade path (older code may say ponytail:).
- Very specific: line 20
If the user names their own marker word (/ponytail-debt TODO), grep for that word instead.
“Common” is measured: kept by at least 6 in 10 of the 54 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
Every deliberate ponytail shortcut is marked with a shortcut: comment naming
its ceiling and upgrade path (older code may say ponytail:). This collects them into one ledger so a deferral
can't quietly become permanent.
Scan
Grep the repo for comment markers, skipping .git and everything the
.gitignore files ignore (dependencies, build output, caches, in any stack):
git grep --no-index --exclude-standard -nE '(#|//|/[*]) ?(shortcut|ponytail):' (add other comment prefixes if your stack uses them)
If the user names their own marker word (/ponytail-debt TODO), grep for that word instead.
Each hit is one ledger row. The comment prefix keeps prose that merely mentions the convention out of the ledger. Skip hits that are not a deferral, like a note about a keyboard shortcut.
Output
One row per marker, grouped by file:
<file>:<line>, <what was simplified>. ceiling: <the limit named>. upgrade: <the trigger to revisit>.
The convention is shortcut: <ceiling>, <upgrade path>, so pull the ceiling
and the trigger straight from the comment. Want an owner per row too? add
git blame -L<line>,<line>.
Flag the rot risk: any marker comment that names no upgrade path or
trigger gets a no-trigger tag, those are the ones that silently rot.
End with <N> markers, <M> with no trigger. Nothing found: No shortcut debt. Clean ledger.
Boundaries
Reads and reports only, changes nothing. To persist it, ask and it writes the
ledger to a file (e.g. PONYTAIL-DEBT.md). One-shot.
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.

