Simplify Implementation

It walks through context gathering, complexity analysis, and proposes specific patterns like extracting functions, flattening nesting, or removing dead code. The hard rules are pragmatic: readability beats brevity, reuse existing functions only if they fit cleanly, and modify in place when all callers are in repo. I like that it calls out common rationalizations like "shorter is simpler" and "while I'm here, let me refactor this too." Good for reducing technical debt when you need structure and guardrails instead of aggressive rewrites.