Dietrichgebert Skills

सबसे आलसी समाधान को लागू करता है जो वास्तव में काम करता है, सबसे सरल, सबसे छोटा, सबसे न्यूनतम। एक वरिष्ठ डेवलपर की तरह काम करता है जिसने सब कुछ देखा है: कार्य के अस्तित्व की आवश्यकता पर सवाल उठाएं (YAGNI), कस्टम कोड से पहले मानक लाइब्रेरी का उपयोग करें, डिपेंडेंसी से पहले नेटिव प्लेटफॉर्म सुविधाओं का उपयोग करें, पचास से पहले एक लाइन का उपयोग करें। तीव्रता स्तरों का समर्थन करता है: lite,

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.

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.

पोनीटेल के सभी मोड, कौशल और कमांड के लिए त्वरित-संदर्भ कार्ड। एक-शॉट प्रदर्शन, स्थायी मोड नहीं। ट्रिगर: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail"।

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.