principle-subtract-before-you-add
From the author
Apply when sequencing an addition, refactor, or rewrite. Remove dead code, redundant validators, and stub references first, then build on the simpler base.
Install
npx skills add backnotprop/pstack --skill principle-subtract-before-you-add -a claude-code
Installs to .claude/skills/principle-subtract-before-you-add/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 90
Security100
Provenance82
Maintenance100
Licence100
Adoption55
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- reuse-before-buildAi-Eastern/reuse-before-buildReuse-first decision gate for coding work. Before building, check whether the project, its platform, its installed dependencies, or a well-evidenced open-source project already provides what is needed, then decide Take, Borrow, or Build from evidence actually read. Use it whenever a task involves choosing an architecture, library, framework, or component; implementing a non-trivial feature, helper, or integration that may already exist; adding, extending, or checking tests; or resuming engineering work from a handoff, checkpoint, or compacted context, even if the user never mentions reuse. Skip it for typos, renames, and other small local edits.Testing★ 99
- principle-foundational-thinkingbacknotprop/pstackApply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.Writing★ 3K
- principle-redesign-from-first-principlesbacknotprop/pstackApply when integrating a new requirement into an existing design.Design★ 3K
- refactorgithub/awesome-copilotSurgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.Engineering★ 40.5K
- code-refactoring-assistantArabelaTso/Skills-4-SESuggest and apply code refactorings to improve readability, maintainability, and code quality. Use this skill when improving existing code structure, eliminating code smells, applying design patterns, simplifying complex logic, extracting duplicated code, renaming for clarity, or preparing code for new features. Provides specific before/after examples, explains benefits, identifies risks, and ensures behavior preservation through tests.Engineering★ 259
- codejeremylongshore/tons-of-skills-marketplaceUse BEFORE generating, refactoring, reviewing, or debugging code. Trigger phrases include "write a function/script/class for X", "review this code/diff/PR", "refactor this", "debug this error", "is this implementation correct", "what's wrong with this code", "improve this code", "translate from X to Y", or any prompt with a code block the user wants you to act on. Also fires when planning architectural changes, picking algorithms or data structures, or evaluating dependency upgrades. Calls the code MCP tool to retrieve an engineering scaffold (failure pattern, procedure, correct-pattern example, verification step) before generating. Catches hallucinated APIs, lost edge cases, premature algorithm commitment, silent contract violations, refactors that change behavior masked by passing tests. Do NOT trigger for pure code reading with no action requested, simple syntax questions, file system operations, running existing tests, or confirming an existing pattern is fine.Engineering★ 2.9K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in