simplification-cascades

Use when complexity is spiraling, implementing the same concept multiple ways, or accumulating special cases - finds one insight that eliminates multiple components: 'if this is true, we don't need X, Y, or Z'. Do NOT use when code is already simple or when complexity is genuinely necessary - premature simplification can remove important edge case handling.