ponytail

Enforces minimal code solutions using standard library and native platform features.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/optimization/ponytail/ponytail
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill ponytail-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate over-engineered abstractions, unnecessary dependencies, and speculative features that create maintenance burden. This Skill forces the simplest working solution by applying a strict decision ladder that questions whether code needs to exist at all before writing it. ## Core Features & Use Cases - YAGNI Decision Ladder: Evaluates every task against six rungs, from "does this need to exist" through stdlib, native platform features, existing dependencies, and one-liners, before writing custom code. - Three Intensity Levels: Lite suggests lazier alternatives while building what's asked, full (default) enforces the ladder with shortest diffs, and ultra challenges requirements themselves with deletion-first thinking. - Deliberate Simplification Markers: Tags intentional shortcuts with ponytail: comments that name the known ceiling and upgrade path, so minimal code reads as intent rather than ignorance. - Use Case: When asked to add a caching layer for API responses, instead of building a custom cache class, the Skill applies @lru_cache(maxsize=1000) in one line and notes when a custom solution would actually be warranted. ## Quick Start Tell the agent to use ponytail mode and solve your next coding task with the simplest solution that works.

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?

Activate ponytail mode to enforce a decision ladder that questions whether code needs to exist, then prefers standard library, native platform features, and one-liners over custom implementations. It blocks unrequested abstractions like single-implementation interfaces and speculative configuration.

What is the difference between ponytail lite, full, and ultra modes?

Lite builds what's asked but names the lazier alternative in one line. Full (the default) enforces the ladder with the shortest working diff and explanation. Ultra is YAGNI-extremist, deleting before adding and challenging the requirement itself.

When should I not use a minimal-code approach?

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 a minimal model cannot anticipate.

Does minimal code mean skipping tests entirely?

No. Non-trivial logic such as branches, loops, parsers, or money and security paths must leave one runnable check behind, like an assert-based self-check or a single small test file. Trivial one-liners need no test since YAGNI applies to tests too.

How do I turn off ponytail mode once activated?

Say "stop ponytail" or "normal mode" to revert to standard behavior. The intensity level persists until changed or the session ends, and you can switch levels anytime with /ponytail lite, full, or ultra.