ponytail

Enforces minimal, YAGNI-driven code changes using stdlib-first solutions and shortest working diffs.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill ponytail-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/ponytail/.openclaw/skills/ponytail
Command: npx skills add https://github.com/amanpal3/SKILLs --skill ponytail-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding assistants often over-engineer solutions by adding unrequested abstractions, new dependencies, and speculative scaffolding. This Skill constrains code generation to the minimum change that actually works, reducing maintenance burden and code bloat. ## Core Features & Use Cases - Solution Ladder: Forces a decision hierarchy from "does this need to exist" through reuse, stdlib, native platform features, and existing dependencies before writing new code. - Intensity Levels: Switchable modes (lite, full, ultra) control how aggressively simplification is applied, with full as the default. - Root-Cause Bug Fixing: Requires tracing all callers of a function before editing, so fixes land once in the shared path instead of patching symptoms. - Use Case: When asked to add a response cache, instead of generating a custom cache class, the Skill applies @lru_cache(maxsize=1000) and notes when a custom cache would become necessary. ## Quick Start Ask the assistant to refactor or implement a coding task with ponytail active, for example: "Add caching to this API fetch function using the simplest approach."

Frequently Asked Questions about ponytail

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

FAQPage Schema
How do I stop AI assistants from over-engineering code?▼

Activate ponytail mode, which enforces a decision ladder: check if the code needs to exist, reuse existing helpers, prefer stdlib and native platform features, then write the minimum working code. Unrequested abstractions like single-implementation interfaces are blocked.

How to switch between ponytail lite, full, and ultra modes?▼

Use the command /ponytail lite, /ponytail full, or /ponytail ultra. Lite builds what is asked but names a lazier alternative, full enforces the ladder with shortest diffs, and ultra challenges the requirement itself before writing anything.

When should I not use minimal-code approaches?▼

Never simplify away input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, or anything explicitly requested. Hardware-facing code also needs calibration knobs that minimal models cannot anticipate.

Does ponytail skip writing tests for code?▼

Non-trivial logic such as branches, loops, parsers, or money and security paths must leave one runnable check, like an assert-based demo or a single small test file. Trivial one-liners need no test, and full test frameworks are avoided unless requested.

How do I turn off ponytail mode?▼

Say "stop ponytail" or "normal mode" to revert to standard behavior. The chosen intensity level otherwise persists until changed or the session ends.