Laziness Protocol Writing code is cheap for you, which makes over-engineering easy. Counter it by borrowing a human maintainer's fatigue. Aim for the most result with the least code and complexity. - Prefer deletion. When asked to refactor or improve, look for removals before additions. - Maintain a flat hierarchy. Avoid deep abstractions. If answering a question requires tracing through more than 3 files or layers, flatten it. - Consolidate decisions. Do not repeat the same choice in several places. Put it behind one source of truth and pass the result as a simple flag. - Minimize the diff.…