ponytail

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

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-sambhav242005
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/Sambhav242005/Major-Project/tree/main/.agents/skills/ponytail
Command: npx skills add https://github.com/Sambhav242005/Major-Project --skill ponytail-sambhav242005

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 - Solution Ladder: A seven-step decision hierarchy that stops at the first sufficient rung, from YAGNI rejection down to minimal new code. - Intensity Levels: Three modes (lite, full, ultra) control how aggressively simplification is enforced, switchable via /ponytail lite|full|ultra. - Root-Cause Bug Fixing: Requires tracing all callers before editing so fixes land once in shared code rather than patched per symptom. - Use Case: When asked to add a response cache, instead of building a custom cache class, the Skill applies @lru_cache(maxsize=1000) and notes in one line what was skipped and when to revisit it. ## Quick Start Ask the assistant to use ponytail mode to implement or refactor a piece of code 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 when writing new code?

Apply a decision ladder: first question whether the feature is needed at all, then check for existing helpers in the codebase, standard library functions, and native platform features before writing anything new. Stop at the first option that works and note what was skipped.

How to choose between standard library and third-party dependencies?

Prefer the standard library whenever it covers the requirement, and use already-installed dependencies before adding new ones. Only introduce a new dependency when a few lines of existing tools genuinely cannot solve the problem.

What are the ponytail intensity levels and how do I switch them?

Ponytail supports lite, full, and ultra modes, with full as the default. Switch levels with /ponytail lite, /ponytail full, or /ponytail ultra; lite suggests lazier alternatives, full enforces the ladder, and ultra challenges the requirement itself.

When should I not apply minimal or lazy solutions?

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 problem; read all affected code before choosing a minimal fix.

Why fix the root cause instead of the reported symptom?

A bug report names a symptom, but sibling callers of the same function often share the defect. Fixing once in the shared code path produces a smaller diff than guarding every caller and prevents the same bug from resurfacing elsewhere.