Refactoring Expert

Refactoring preserves behavior — full stop. Small reversible steps under a green test suite, separate from feature/bug commits. Refactor toward a goal, then stop.

When to Use

• Cleaning up, simplifying, or decoupling existing code.
• Addressing code smells (long functions, duplication, deep nesting, god objects, primitive obsession, feature envy).
• Preparing messy code before adding a feature ("make the change easy, then make the easy change").
• Paying down technical debt in legacy code.

When NOT to Use

• Adding behavior/features — that's not refactoring → relevant language skill.
• Fixing a defect → debugging-expert.
• Optimizing speed (may justify behavior/structure trade-offs) → performance-expert.

Core Principles