ponytail

Enforces minimal code solutions by applying YAGNI, reuse, and stdlib-first principles.

9|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/jerrylin96/dotgemini --skill ponytail-jerrylin96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/jerrylin96/dotgemini/tree/main/skills/ponytail
Command: npx skills add https://github.com/jerrylin96/dotgemini --skill ponytail-jerrylin96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate bloat from speculative abstractions, duplicated helpers, and unnecessary dependencies. This Skill keeps every code writing, refactoring, or bug-fixing response focused on the smallest working solution. ## Core Features & Use Cases - Always-Active Minimization: Applies a seven-rung decision ladder (YAGNI, reuse, stdlib, native features, existing dependencies, one-liners, minimal code) to every coding response. - Root-Cause Bug Fixing: Traces all callers of a function before editing so fixes land once in shared code instead of patching symptoms per caller. - Adjustable Intensity: Supports lite, full, and ultra modes switchable via /ponytail lite|full|ultra, with full as the default. - Use Case: When asked to add a feature, the Skill first checks whether existing helpers or the standard library already cover it, then ships the shortest working diff instead of scaffolding new abstractions. ## Quick Start Ask the assistant to write or fix any code and it will automatically apply ponytail's minimal-solution rules, or say "ponytail ultra" to maximize strictness.

Frequently Asked Questions about ponytail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid over-engineering code with AI assistants?

Use a minimization skill that applies YAGNI and reuse-first rules to every response. Ponytail checks whether code needs to exist, whether the codebase or stdlib already solves it, and ships the shortest working diff instead of speculative abstractions.

How to fix bugs at the root cause instead of patching symptoms?

Grep every caller of the function you plan to edit before making changes. A single guard in the shared function is a smaller diff than guards in every caller, and patching only the reported path leaves sibling callers broken.

Can I adjust how strict the code minimization is?

Yes, the skill supports lite, full, and ultra modes via /ponytail lite|full|ultra, with full as the default. Saying "stop ponytail" or "normal mode" deactivates it entirely.

When should I not use a YAGNI-first coding approach?

Avoid it when requirements genuinely demand extensibility, such as public APIs with committed contracts or performance-critical paths needing upfront design. The ladder runs after understanding the problem, not instead of it.

Does minimal code generation skip understanding the problem first?

No, the skill requires reading the task and tracing the real flow end to end before applying the minimization ladder. The first lazy solution that works is chosen only after knowing what the change must touch.