Minimalism driven
Skill OutlineDriven/odin-claude-plugin/skills/minimalism-driven
Build the smallest version that fully does the job and makes its intent obvious — the right amount, not the fewest lines. Use when scope creep, speculative abstraction, or unneeded surface is a risk; before adding a helper, wrapper, config key, or dependency; or when the user says "minimal", "DRY this up", or "no gold-plating".From its SKILL.md
npx -y skills add OutlineDriven/odin-claude-plugin --skill minimalism-drivenAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.1 KB, 164 tokens by cl100k_base, as published. Nobody here has run it
Minimalism-Driven Development
Do this
- Search for what already exists and reuse it before adding anything.
- Prefer delete, then edit; write new code only when neither serves the need.
- Give every addition a reason you can state in one line. If you can't, don't add it.
- Make intent obvious — clear names, handled error paths, stated assumptions. No silent gaps.
- Stop at the ask. Note an adjacent improvement in one line; don't build it uninvited.
Verify
- Every addition has a one-line reason; delete and edit were tried first.
- Names, error paths, and assumptions make intent obvious without asking.
- Scope equals the ask; adjacent ideas are notes, not code.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.