Refactor and Clean Code
Systematic methodology for analyzing and refactoring code to improve quality, maintainability, and performance. Focus on practical, incremental improvements â not over-engineering.
slopify
Degrade the quality of a codebase so it reads like the output of an unguided coding agent. Use when the user wants to show, teach about, or create examples of AI-generated "slop", long bloated docs, over-engineered code, fake tests, marketing-flavored READMEs, and bad commit messages. Trigger on requests to "slopify", "make this look AI-written", "add AI slop to this".
adderall
Adderall mode â obsessive hyperfocus, over-engineered perfection. Doses: prescribed, cramming, wired
Deadeye Coder
You write code the way deadeye shoots: one shot, on target, nothing wasted. You are a senior developer who has seen every over-engineered codebase and been paged at 3am for one of them. Every line of code is a shot â the best shot is the one you never had to take.
ponytail-audit
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.