Subtract Before You Add
When evolving a system, remove complexity first, then build.
Why: Adding to a complex system compounds complexity. Removing first leaves less code, reveals the essential structure, and usually makes the next design obvious. Default to subtraction.
Make simplification a continual investment. Leave the design slightly simpler and more capable behind the same or smaller surface than you found it.
The pattern:
- Sequence removal before construction
- Cut before you polish (get to the minimum before investing in quality)
- Design for observed usage, not speculative edge cases
- No speculative validators, parsers, or guards beyond what the spec demands
- Simplify prompts (remove redundant instructions, excessive templates)
- When a reference has no novel content, delete it rather than leaving a stub
This repository (Asymmetric-al/core)
Vendored from p3-stack (MIT) at commit 09909eb. Provenance is in references/upstream.md. On conflict, the current user request, root AGENTS.md, the nearest nested AGENTS.md, and the matching docs/ai/rules/* rulebook win over this skill.
- Explicit invocation only: use it when the user invokes
/principle-subtract-before-you-add (Claude Code, Cursor, T3 Code) or $principle-subtract-before-you-add (Codex), or when an invoked p3-stack skill routes here. Do not route other work to it.
- Confirm before outward-facing or hard-to-reverse actions such as pushing, merging, deploying, deleting, or posting messages, unless the user authorized that action for this task.
Edit this canonical copy in docs/ai/skills/principle-subtract-before-you-add/, then run bun run skills:sync and bun run skills:verify.
1---2name: principle-subtract-before-you-add3description: "Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base."4disable-model-invocation: true5metadata:6 source: https://skillmd.com/skills/asymmetric-al/principle-subtract-before-you-add7---89# Subtract Before You Add1011When evolving a system, remove complexity first, then build.1213**Why:** Adding to a complex system compounds complexity. Removing first leaves less code, reveals the essential structure, and usually makes the next design obvious. Default to subtraction.1415Make simplification a continual investment. Leave the design slightly simpler and more capable behind the same or smaller surface than you found it.1617**The pattern:**1819- Sequence removal before construction20- Cut before you polish (get to the minimum before investing in quality)21- Design for observed usage, not speculative edge cases22- No speculative validators, parsers, or guards beyond what the spec demands23- Simplify prompts (remove redundant instructions, excessive templates)24- When a reference has no novel content, delete it rather than leaving a stub2526<!-- CORE-OVERLAY-START -->2728## This repository (Asymmetric-al/core)2930Vendored from [p3-stack](https://github.com/uzairansaruzi/p3-stack) (MIT) at commit `09909eb`. Provenance is in `references/upstream.md`. On conflict, the current user request, root `AGENTS.md`, the nearest nested `AGENTS.md`, and the matching `docs/ai/rules/*` rulebook win over this skill.3132- Explicit invocation only: use it when the user invokes `/principle-subtract-before-you-add` (Claude Code, Cursor, T3 Code) or `$principle-subtract-before-you-add` (Codex), or when an invoked p3-stack skill routes here. Do not route other work to it.33- Confirm before outward-facing or hard-to-reverse actions such as pushing, merging, deploying, deleting, or posting messages, unless the user authorized that action for this task.3435Edit this canonical copy in `docs/ai/skills/principle-subtract-before-you-add/`, then run `bun run skills:sync` and `bun run skills:verify`.3637<!-- CORE-OVERLAY-END -->