ponytail-help
Quick-reference card for the ponytail modes and skills installed from the behavior pack. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
- License 许可
- MIT
- 最近更新
- 2026-10-03
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ponytail-help
- license
- MIT
- description
- Quick-reference card for the ponytail modes and skills installed from the behavior pack. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
02 资源文件 2
- 许可证LICENSE1.0 KB
- 参考文档UPSTREAM.md1.3 KB
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-help | /ponytail-help |
This card. |
Claude Code and OpenCode both expose installed skills as slash commands with these names.
Deactivate
Say "stop ponytail" or "normal mode". Resume anytime with /ponytail.
Scope note
Ponytail optimizes for less code. It does not replace correctness, security or design review; use the normal review skills for those.
04 同仓库更多 Skills
web-design-guidelines
Review UI code against the Web Interface Guidelines (accessibility, focus, forms, motion, typography, performance, copy). Use when asked to review a UI, check accessibility, audit a design or UX, or check a site against best practices.
using-agent-skills
Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
spec-driven-development
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
security-and-hardening
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services. Use when auditing dependencies for known vulnerabilities, triaging package-manager audit findings, or assessing supply-chain risk in a new package. Use when personal data or privacy compliance (GDPR, CCPA) is involved.