ponytail

Enforces minimal, standard-library-first solutions for coding tasks with adjustable intensity levels.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill ponytail-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/ponytail
Command: npx skills add https://github.com/avel123111/triplanio --skill ponytail-avel123111

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 for any coding task by applying a strict decision ladder: question whether the work is needed at all (YAGNI), reuse existing code, prefer the standard library and native platform features, and only write new code as a last resort. ## Core Features & Use Cases - Minimal-Solution Ladder: A seven-step decision hierarchy that stops at the first rung that works, from YAGNI elimination down to the minimum code that solves the problem. - Adjustable Intensity Levels: Three modes (lite, full, ultra) control how aggressively simplification is enforced, from suggesting lazier alternatives to challenging the requirement itself. - Root-Cause Bug Fixing: Directs fixes to the shared function all callers route through rather than patching individual symptoms. - Use Case: When asked to add a response cache, instead of building a custom cache class, the Skill applies a one-line @lru_cache(maxsize=1000) and notes when a custom solution would actually be warranted. ## Quick Start Ask the AI to implement or refactor any piece of code using ponytail mode, for example by saying "use ponytail to add caching to this API client".

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 when writing new code?

Apply a decision ladder before writing anything: check if the feature is needed at all, reuse existing helpers in the codebase, prefer standard library and native platform features, and only then write the minimum code that works. Stop at the first rung that solves the problem.

How to choose between a standard library solution and a new dependency?

Prefer the standard library or an already-installed dependency whenever it covers the requirement. Never add a new dependency for something a few lines of code can accomplish, and only introduce one when existing options measurably fall short.

What are the ponytail intensity levels lite, full, and ultra?

Lite builds what is asked but names a lazier alternative in one line. Full, the default, enforces the minimal-solution ladder with the shortest diff and explanation. Ultra aggressively deletes before adding and challenges the requirement itself.

When should I not simplify code with a minimal approach?

Never simplify away input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, or anything explicitly requested. Also never skip understanding the full problem and code flow before choosing a minimal fix.

Why fix bugs at the root cause instead of the reported symptom?

A bug report names a symptom, but patching only that path leaves sibling callers broken. Fixing the shared function every caller routes through produces a smaller total diff and resolves the issue once for all call sites.