name: principle-subtract-before-you-add description: "Apply before an addition or refactor. Remove dead weight first, then build on the simpler base."

Subtract Before You Add

Remove complexity first, then add. Deletion yields a smaller base, which makes the next change smaller and less brittle.

Why: Adding onto a messy system compounds the mess. Cutting first reveals the essential structure, and the next design is usually obvious.

Pattern:

• Sequence removal before construction.
• Delete dead code, one-caller wrappers, redundant validators, and stub references first.
• Design for observed usage, not speculative edge cases.
• No speculative guards beyond what the spec demands.
• When a file or instruction has no novel content, delete it rather than leaving a stub.
• Leave the design slightly simpler behind the same or smaller surface than you found it.
• Cut before you polish. Get to the minimum before investing in quality.