simplifylisted

# Simplify — Code Simplification ## When to Trigger - File exceeds 200 lines - Function exceeds 40 lines - Deeply nested code (3+ levels) - Copy-pasted blocks detected - "This is getting hard to follow" feeling ## Process ### 1. Measure - Line count, function count, nesting depth - Identify the longest/most complex function **Why**: You cannot improve what you cannot quantify. Baseline metrics prove simplification actually happened and prevent subjective "it feels cleaner" claims. ### 2. Extract - **Extract function**: Turn a code block into a named function - **Extract constant**: Replace magic numbers/strings - **Extract module**: Split large files by responsibility **Why**: Named abstractions replace "what does this block do?" with "what does this function promise?" — reducing cognitive load per reading unit. ### 3. Rename - Variables: describe what it holds, not how it's computed - Functions: describe what it does, not how - Files: match the primary export/class **Why**: Precise names eliminate the need for comments and make wrong code look wrong. A reader should understand intent from names alone. ### 4. Reduce - Remove dead code (unused imports, unreachable branches) - Replace imperative loops with declarative (map, filter, reduce) - Merge duplicate logic into shared utility **Why**: Every line of code is a line someone must read, understand, and maintain. Fewer lines with the same behavior means lower lifetime cost. ### 5. Verify - All tests still pass after