Principle Subtract Before You Add
- 410 installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
Simplify Cursor plugin scope by removing dead code, redundant settings, and overlapping commands before introducing new capabilities or configuration.
About
Subtract-before-you-add principle for Cursor plugins: remove redundant commands, settings, and code paths before adding features so the extension stays minimal, testable, and easier for users to adopt.
- Delete unused commands first
- Collapse overlapping settings
- Prefer smaller public API
- Reduce cognitive load
- Justify every new surface
Principle Subtract Before You Add by the numbers
- 410 all-time installs (skills.sh)
- Ranked #257 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill principle-subtract-before-you-addAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 410 |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
What it does
Simplify Cursor plugin scope by removing dead code, redundant settings, and overlapping commands before introducing new capabilities or configuration.
Files
Subtract Before You Add
When evolving a system, remove complexity first, then build. Deletion gives you a simpler base, which makes the next addition smaller and less brittle.
Why: Adding to a complex system compounds complexity. Removing first cuts the surface area, reveals the essential structure, and usually makes the next design obvious. Default to subtraction.
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
- Out-of-spec features drag validators behind them. Persistence, retry-on-startup, and schema migration each need guards to defend their inputs.
- Simplify prompts (remove redundant instructions, excessive templates)
- When a reference has no novel content, delete it rather than leaving a stub
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264k