simplify-code

Replace nested conditionals with early returns and guard clauses to reduce indentation levels. Combine this with array methods like filter and forEach to express logic declaratively, targeting three or fewer nesting levels.

Remove unused imports, unreachable branches, commented-out code, and stale feature flags first since these are the safest changes. Always run the existing test suite and build afterward to confirm behavior is preserved.

Avoid simplifying performance-critical hot paths, patterns required by frameworks, explicitly requested architectures, or abstractions preparing for known near-term growth. Ask the user before removing a pattern that may exist for a deliberate reason.

Common signs include wrapper classes that only delegate, factories creating a single type, interfaces with one implementation, functions with more than four parameters, and custom caches for tiny datasets. These add cognitive load without delivering value.

It should not if done correctly. The simplification protocol requires running the full test suite and build after changes, and simplifying incrementally so any breakage is immediately isolated and reversible.