principle-subtract-before-you-add

Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.

4,752
installs: 0 up / 0 down, score 0.00
votes: 2,555
repo stars
Updated: less than a month ago
In the catalog since: 5 Oct 2026
From: backnotprop/pstack

Get it through your agent npx skills add backnotprop/pstack@principle-subtract-before-you-add

Skill instructions

Rendered from the published SKILL.md, 13 lines.

Subtract Before You Add

When evolving a system, remove complexity first, then build. 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.

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

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "principle-subtract-before-you-add"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository backnotprop/pstack
Listing on skills.sh

From backnotprop/pstack via skills.sh

Related skills

principle-subtract-before-you-add
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
4,148 installs
principle-sequence-verifiable-units
Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.
3,920 installs
simplify
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
19,933 installs
principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
4,752 installs
code-simplify
Use for simplifying recently changed code: clean up, refactor for clarity, reduce complexity, improve readability, or maintainability.
2,310 installs

More from backnotprop/pstack

unslop
Cut AI tells from any writing.
6,122 installs
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
5,259 installs
principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
5,197 installs
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
5,178 installs
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
5,100 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.