ponytail-help
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
- License 许可
- MIT
- 最近更新
- 2026-10-21
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ponytail-help
- description
- Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
03 SKILL.md 正文
Ponytail Help
Display this reference card when invoked. One-shot, do NOT change mode, write flag files, or persist anything.
Levels
| Level | Trigger | What change |
|---|---|---|
| Lite | /ponytail lite |
Build what's asked, name the lazier alternative in one line. |
| Full | /ponytail |
The ladder enforced: YAGNI → stdlib → native → one line → minimum. Default. |
| Ultra | /ponytail ultra |
YAGNI extremist. Deletion before addition. Challenges requirements before building. |
Level sticks until changed or session end.
Skills
| Skill | Trigger | What it does |
|---|---|---|
| ponytail | /ponytail |
Lazy mode itself. Simplest solution that works. |
| ponytail-review | /ponytail-review |
Over-engineering review: L42: yagni: factory, one product. Inline. |
| ponytail-audit | /ponytail-audit |
Whole-repo over-engineering audit: ranked list of what to delete. |
| ponytail-debt | /ponytail-debt |
Harvest ponytail: shortcut comments into a tracked ledger. |
| ponytail-gain | /ponytail-gain |
Measured-impact scoreboard: less code, less cost, more speed. |
| ponytail-help | /ponytail-help |
This card. |
In Codex CLI and the IDE extension, invoke skills with $ponytail:ponytail,
$ponytail:ponytail-review, or $ponytail:ponytail-help. Claude Code and OpenCode use the
slash-command forms above (OpenCode ships all six as slash commands).
Deactivate
Say "stop ponytail" or "normal mode". Resume anytime with /ponytail.
/ponytail off also works.
Configure Default Mode
Default mode = full, auto-active every session. Change it:
Environment variable (highest priority):
export PONYTAIL_DEFAULT_MODE=ultra
Config file (~/.config/ponytail/config.json, Windows: %APPDATA%\ponytail\config.json):
{ "defaultMode": "lite" }
Set "off" to disable auto-activation on session start, activate manually
with /ponytail when wanted.
Resolution: env var > config file > full.
Update
Enable auto-update once: open /plugin, go to Marketplaces, pick ponytail, Enable auto-update. Claude Code then pulls new versions at startup (run /reload-plugins when it prompts). Manual refresh: /plugin marketplace update ponytail then /reload-plugins.
If /plugin is not recognized, your Claude Code is out of date. Update it (npm install -g @anthropic-ai/claude-code@latest, or brew upgrade claude-code) and restart. Other hosts use their own update flow.
More
Full docs + examples: https://github.com/DietrichGebert/ponytail
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.