principle-subtract-before-you-add

What problem does it solve? When evolving a codebase, teams often add features on top of existing complexity, which compounds technical debt and makes every subsequent change more brittle. This Skill enforces a subtraction-first sequencing principle so additions land on a simpler, smaller base. ## Core Features & Use Cases - Removal-before-construction sequencing: Delete dead weight, redundant validators, and stub references before building anything new. - Anti-speculation guardrails: Blocks speculative validators, parsers, and guards beyond what the spec demands, and cuts out-of-spec features like unneeded persistence or retry logic. - Prompt and reference simplification: Removes redundant instructions, excessive templates, and stub references with no novel content. - Use Case: Before refactoring a module or adding a feature, apply this principle to strip unused code paths first, making the new design smaller and less brittle. ## Quick Start Ask the assistant to apply the subtract-before-you-add principle to review the current module and remove dead code before implementing the planned feature.