From subtract
Critique a plan, design, process, or document through a subtractive lens. USE WHEN user asks to simplify, cut, focus, reduce, tighten, or critique something for bloat — or when reviewing plans, processes, or designs that feel overbuilt.
How this skill is triggered — by the user, by Claude, or both
Slash command
/subtract:subtractThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When improving something, people systematically default to adding and overlook removing ([Adams et al., 2021](https://www.nature.com/articles/s41586-021-03380-y)). This skill forces the opposite. Dieter Rams: "Less, but better." Strunk & White: "Omit needless words."
When improving something, people systematically default to adding and overlook removing (Adams et al., 2021). This skill forces the opposite. Dieter Rams: "Less, but better." Strunk & White: "Omit needless words."
For each component of what you're reviewing:
Then propose the simplified version. Fewer steps that each do real work beat many steps that feel productive.
npx claudepluginhub taivop/marketplace --plugin subtractStrips away non-essential layers from strategies, designs, messages, or processes to reveal what matters most. Useful when reviewing things that feel cluttered or unfocused.
Identifies and removes non-essential elements, fragilities, and complexity in systems, products, or processes. Use for improving by subtraction rather than addition.
Applies the via negativa principle of subtraction-over-addition when improving systems, features, or processes. Use before adding anything to pause and ask what to remove instead.