ponytail-gain
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the agentic benchmark averages. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ponytail-gain
- description
- Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the agentic benchmark averages. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
03 SKILL.md 正文
Ponytail Gain
Display this scoreboard when invoked. One-shot: do NOT change mode, write flag files, or persist anything.
The figures are the published agentic benchmark averages: a headless Claude
Code session (Haiku 4.5) doing 12 feature tickets on a real FastAPI + React
repo, each task averaged over 4 runs, against the same agent without the
skill, plus 6 safety tasks. They are measured, not computed from the current
repo. Source: benchmarks/results/2026-06-18-agentic.md and the README.
Scoreboard
Render plain ASCII bars. The bar length shows ponytail as a share of the no-skill baseline; the label carries the exact figure:
ponytail gain benchmark average · 12 tasks · Haiku 4.5
no-skill ████████████████████ 100%
Lines of code █████████··········· 46% ▼ 54%
Tokens ████████████████···· 78% ▼ 22%
Cost ████████████████···· 80% ▼ 20%
Time ███████████████····· 73% ▼ 27%
Safety kept 100% (validation, error handling, security)
This repo: /ponytail-debt (shortcuts you deferred)
/ponytail-audit (what's still cuttable)
Honesty boundary
These are benchmark averages, not this repo. NEVER print a per-repo savings
number ("you saved X lines/tokens here"): the unbuilt version was never
written, so there is no real baseline to subtract from in a live repo. The
only real per-repo figures come from /ponytail-debt (a counted ledger), and
this card points there instead of inventing one.
Boundaries
One-shot display. Edits nothing, changes no mode. "stop ponytail" or "normal mode": revert.
04 同仓库更多 Skills
use-garden
Consulting garden, the separately installed guidance command this repository's owner enabled, when an open engineering choice the repository does not settle, made in a change or only recommended, would be informed by published guidance. Use for a choice between approaches, a pattern or pitfall for a technology or concern the work touches, or a unit a repository decision names; not for a question about this repository's own facts or a change whose choices are already settled.
use-garden
Consulting garden, the separately installed guidance command this repository's owner enabled, when an open engineering choice the repository does not settle, made in a change or only recommended, would be informed by published guidance. Use for a choice between approaches, a pattern or pitfall for a technology or concern the work touches, or a unit a repository decision names; not for a question about this repository's own facts or a change whose choices are already settled.
what-to-build
Propose what this product could do next at three altitudes: sharpen a shipped slice, extend one, or open ground the product does not stand on yet. Use for 'what should we build next', 'any ideas for this app', 'what's missing', 'is this done or is there more in it', and quick-win hunts. Not for refactors, which belong to the architecture survey.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets in a plan directory's map.md, and resolve them one at a time until the way to the destination is clear.
verify
Prove a change's claims with fresh evidence: restate each item of its acceptance so it can fail, capture a baseline and a treatment with the same command, compare the raw artifacts, and return VERIFIED, NOT VERIFIED or INCONCLUSIVE for each, at the depth the change's mode gives the verify step. Use when the mode reaches verify, or when the owner says "verify this", "prove it works" or "did this fix it".
tdd
Test-first development at any step: discover the repository's own test commands, name the break a test catches, watch it fail for the intended reason, make it pass with the smallest change, and add a new test only where it catches a realistic failure the existing ones would miss. Use when writing or changing a test, building a feature or fixing a bug test-first, or deciding whether a change needs a new test; also on 'red-green-refactor' and integration tests.