ponytail

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

166|78|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-engasnm111
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ponytail
Source: https://github.com/engasnm111/lnwjud/tree/main/.agents/skills/ponytail
Command: npx skills add https://github.com/engasnm111/lnwjud --skill ponytail-engasnm111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate over-engineered abstractions, unnecessary dependencies, and boilerplate 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 option, from deleting the requirement down to writing minimal new code. - Intensity levels: Three modes (lite, full, ultra) control how aggressively simplification is enforced, switchable at any time with "/ponytail lite|full|ultra". - Root-cause bug fixing: Traces all callers of a function before editing so one guard in shared code replaces patches in every caller. - 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 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?▼

Use a minimal-solution enforcement skill that applies a YAGNI decision ladder: question whether the task is needed, reuse existing code, prefer the standard library and native platform features, and write new code only as a last resort. Ponytail implements this with three intensity levels.

How to reduce unnecessary dependencies in a project?▼

Audit each requested feature against what the standard library, native platform features, and already-installed packages provide before adding anything new. The ponytail ladder makes this a reflex: a new dependency is only justified when a few lines of existing tooling cannot do the job.

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

Lite builds what is asked but names the lazier alternative in one line. Full, the default, enforces the ladder with the shortest working diff. Ultra is YAGNI-extremist, preferring deletion over addition and challenging the requirement itself.

When should I not use a minimal-solution approach?▼

Never simplify away input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, or anything explicitly requested. The approach also requires fully understanding the problem and tracing all callers before choosing the smallest fix.

Does ponytail write tests for minimal code?▼

Non-trivial logic such as branches, loops, parsers, or money and security paths gets one runnable check, typically an assert-based self-check or a single small test file. Trivial one-liners get no test, and no frameworks or fixtures are added unless requested.