Apply when sequencing an addition, refactor, or rewrite. Remove dead weight, redundant validators, and stub references first, then build on the simpler base.
NewMaintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Coding pack
Last verified 9/27/2026
What it changes
Passed 19 of 22 test cases with the skill, and 19 of 22 without it.
Model gemini-3.6-flashMeasured 9/27/2026v219 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
I need to add support for custom webhook notifications in `notification_service.js`. The current file has several stub functions and unused formatting helpers from an old notification attempt. Please update the service so it fulfills the new webhook feature.
What was checked, without and with the skill
Checked
Without skill
With skill
removes unused stub functions from notification_service.js
case-02 · gemini-3.6-flash · 9/27/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md15 linessingle file
Subtract Before You Add
When evolving a system, remove complexity first, then build.
Why: Adding to a complex system compounds complexity. Removing first leaves less code, reveals the essential structure, and usually makes the next design obvious. 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.
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