Code Simplification

Refactoring code without breaking it is harder than it looks, and this skill gives you a structured way to do it. It's built around five principles: preserve behavior exactly, follow your project's conventions, prefer clarity over cleverness, don't over-simplify, and scope your changes to what actually needs work. The process is concrete: understand why the code exists (Chesterton's Fence), identify specific patterns like deep nesting or misleading names, then apply changes incrementally with tests running after each one. The honest take is that simplification isn't about fewer lines, it's about whether a new team member would understand your code faster than the original. Good for post-feature cleanup and code review.