19 skills published by 0xwilliamortiz across 5 repositories. Together they weigh 1 249 950 tokens — that is what loading all of them at once would cost you in context.
19 skills 1 249 950 tokens total
> Enforces a measured complexity budget on coding work. Reaches for the standard library, native platform features and code that already exists in the repository before writing anything new, and treats every added dependency, file and line as a cost that has to be justified. A hook measures the real diff and reports overruns back mid-task, so the budget is fixing, reviewing, choosing libraries, or designing an interface. Use it whenever the user says "ratchet", "keep it minimal", "simplest thing that works", "yagni", "don't over-engineer", "smallest diff", or complains about bloat, boilerplate, scaffolding or dependency creep. Do not use it for non-coding requests.
> ledger at .ratchet/ledger.jsonl, the accepted complexity mark, and every upgrade trigger. Use when the user says "ratchet ledger", "/ratchet-ledger", "what did we defer", "show the complexity trend", "what shortcuts are in here", or asks whether the codebase is getting simpler or more complex over time. Reports real recorded numbers only, never estimates.
> Reviews a diff or a whole repository for over-engineering only, and returns a delete list rather than prose. Finds reinvented standard library calls, dependencies the platform already covers, abstractions with one implementation, wrappers that only forward, configuration nothing reads and dead flexibility. Use whenever the user says "review for over-engineering", "what can we delete", "is this over-engineered", "find the bloat", "audit this repo", or invokes /ratchet-review. Pair it with a normal correctness review, it deliberately does not look for bugs.
Collect and synthesize opinions from multiple AI agents. Use when users say "summon the council", "ask other AIs", or want multiple AI perspectives on a question.
Audit the whole repo for over-engineering. A ranked list of what to delete, simplify, or replace with stdlib or native features.
Harvest every ponytail: shortcut comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.
Show ponytail measured impact as a scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display.
Quick reference for ponytail's modes, skills, and commands. One-shot display.
Review a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.
Lazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.
> Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
> Whole-repo audit for over-engineering. Like ponytail-review, but scans the 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.
> 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.
> cost, more speed, from the benchmark medians. One-shot display, not a "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
> Quick-reference card for all ponytail modes, skills, and commands. "ponytail help", "what ponytail commands", "how do I use ponytail".
> reinvented standard library, unneeded dependencies, speculative abstractions, 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.
> Forces the laziest solution that actually works, simplest, shortest, most task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before 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).
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, and filler phrases.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.