Skills by dietrichgebert

• A
  ponytailDietrichGebert/ponytail · 147k

  Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

• A
  ponytailDietrichGebert/ponytail · 147k

  Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.

• A
  ponytail-auditDietrichGebert/ponytail · 147k

  Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.

• A
  ponytail-auditDietrichGebert/ponytail · 147k

  Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.

• A
  ponytail-debtDietrichGebert/ponytail · 147k

  Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.

• A
  ponytail-debtDietrichGebert/ponytail · 147k

  Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.

• A
  ponytail-gainDietrichGebert/ponytail · 147k

  Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".

• A
  ponytail-gainDietrichGebert/ponytail · 147k

  Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.

• A
  ponytail-helpDietrichGebert/ponytail · 147k

  Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".

• A
  ponytail-helpDietrichGebert/ponytail · 147k

  Quick reference for ponytail's modes, skills, and commands. One-shot display.

• A
  ponytail-reviewDietrichGebert/ponytail · 147k

  Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.

• A
  ponytail-reviewDietrichGebert/ponytail · 147k

  Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.

All agent skills →