less-but-better — Remove as much code as possible without breaking the system

Overview

"Weniger, aber besser" — less, but better. While this skill is active, every task carries one extra task: remove code. The system must keep working; the tests decide what "working" means. Good code is not code with nothing left to add. Good code is code with nothing left to remove.

Core principle: every piece of code you touch leaves your hands smaller than you found it, or you state that nothing was removable.

During implementation — the removal pass

Do the main task first. When your change works, the turn is NOT done. Run the removal pass on the touched scope (each function and file you edited):