Verified Agent Skill record

ponytail

A coding skill that enforces minimal, lazy-but-correct solutions across writing, refactoring, fixing, reviewing, and designing code. Applies a priority ladder from YAGNI through codebase reuse, standard library, native platform features, existing dependencies, and one-liners before writing new code. Supports three intensity levels: lite, full (default), and ultra.

Tasks

Refactor over-engineered code by replacing custom implementations with standard library or native platform features
Review pull requests to identify unnecessary abstractions, speculative scaffolding, and re-implementations of existing codebase helpers
Fix bugs by tracing root causes through all callers rather than patching the reported symptom path alone

Inputs

A coding task description: writing, adding, refactoring, fixing, reviewing, or designing code
Optional intensity level argument: lite, full (default), or ultra
Trigger phrases from the user such as: ponytail, be lazy, lazy mode, simplest solution, minimal solution, yagni, do less, shortest path, or complaints about over-engineering, bloat, boilerplate, or unnecessary dependencies

Outputs

Code as the primary output, placed first
At most three short lines following a pattern of skipped alternatives and when to add them: skipped: [X], add when [Y]
For non-trivial logic: one minimal runnable check such as an assert-based demo() or __main__ self-check, or one small test_*.py file
Deliberate simplifications marked with a ponytail: comment naming the ceiling and upgrade path

Limitations and checks

Must not be used for non-coding requests including general knowledge, prose, translation, summaries, or recipes
Must never simplify away input validation at trust boundaries, error handling that prevents data loss, security measures, or accessibility basics
Governs what is built, not how prose is communicated
Verify no unrequested abstractions were introduced: no interface with a single implementation, no factory for one product, no config for a never-changing value
Confirm the solution stops at the first rung of the ladder that holds: YAGNI check, codebase reuse check, stdlib check, native platform check, existing dependency check, one-liner check, then minimum code
Verify that non-trivial logic (a branch, a loop, a parser, a money/security path) has one runnable check left behind: an assert-based demo() or __main__ self-check, or one small test_*.py
Confirm deliberate simplifications that cut real corners are marked with a ponytail: comment naming the ceiling and upgrade path
Verify the explanation does not exceed three short lines and follows the skipped/add-when pattern