prefer-less

Goal

Every change should avoid unnecessary code and concepts. Prefer leaving the codebase smaller when that preserves clarity, behavior, and the requested outcome. When more code is required, keep the addition as small as the request allows.

Required Behavior

• Must stay inside the scope the user actually asked for.
• Must measure success by the codebase's end state, not by patch effort or familiarity.
• Must inspect the final diff hunk by hunk and revert hunks not required by the request.
• Prefer deletion, inlining, or making code obsolete when end-state is smaller.
• Prefer keeping abstractions that earn their cost; never inline just to reduce lines.
• Must preserve exact behavior in polish mode unless the user asked for a change.
• Must challenge net code increases; proceed only when added code is required.
• Never rewrite working untouched code as a side effect of another task.
• Never use passing tests to justify unrelated rewrites.
• Never add flexibility, layers, or types without a concrete expected use.
• Never treat fewer lines as proof code is simpler; clarity wins ties.