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,235
installs: 0 up / 0 down, score 0.00
votes: 13,528
repo stars
Updated: less than a month ago
In the catalog since: 1 Oct 2026
From: cursor/plugins

Get it through your agent npx skills add cursor/plugins@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 cursor/plugins
Listing on skills.sh

From cursor/plugins via skills.sh

Related skills

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.
4,006 installs
principle-redesign-from-first-principles
Apply when integrating a new requirement into an existing design.
4,262 installs
code-simplify
Use for simplifying recently changed code: clean up, refactor for clarity, reduce complexity, improve readability, or maintainability.
2,310 installs
build
Plan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, implement, execute the spec, or tackle a specific §T task (`build §T.3`, `build --next`, `implement next task`, `run the build`). Expects SPEC.md to exist; if not, defers to the spec skill.
2,681 installs
simplify
Simplify and refine recently modified code for clarity and consistency. Use after writing code to improve readability without changing functionality.
20,058 installs

More from cursor/plugins

unslop
Cut AI tells from any writing.
27,770 installs
thermo-nuclear-code-quality-review
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
22,194 installs
deslop
Remove AI-generated code slop and clean up code style
9,336 installs
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
7,883 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,933 installs

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

To request removal, use the contact form.