keep-it-simple

To simplify complex code, provide the messy snippet and request a plain text rewrite that preserves behavior. This replaces overcomplicated logic with straightforward control flow and explicit intent, ensuring readability and maintainability without unnecessary cleverness.

Refactoring without over-architecting means favoring clarity over complexity and applying the rule of simplicity first. You enforce straightforward implementations and explicit control flow to replace overcomplicated logic with clear, maintainable alternatives across feature work and maintenance tasks.

Clever code hurts maintainability because it obscures explicit intent and complicates control flow. Resisting cleverness by favoring clarity ensures straightforward implementations, making the codebase easier to read, maintain, and refactor without untangling unnecessary complexity.

Yes, you can enforce simple boundaries during feature development by emphasizing readability, straightforward control flow, and explicit intent. This prevents complexity from creeping into typical software tasks and ensures straightforward implementations across maintenance and refactoring work.

You should not use clever or overly abstract implementations when they compromise readability and maintainability. Applying simplicity first ensures explicit control flow and straightforward implementations, resisting over-architecting solutions across refactoring, feature work, and maintenance tasks.