Keep it simple
Write the simplest code that solves the actual problem — avoid over-engineering. Use whenever writing or reviewing code, especially when tempted to add abstraction, config, or generality "for the future". Favors boring, direct, minimal solutions.From its SKILL.md
npx -y skills add vaibhavsaxena022/skills --skill keep-it-simpleAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, 210 tokens by cl100k_base, as published. Nobody here has run it
Keep It Simple
Solve today's problem in the most boring, direct way. Complexity has to earn its place.
Do
- Write the smallest change that satisfies the requirement.
- Prefer plain functions and direct code over layers of indirection.
- Introduce an abstraction only after you see 2–3 real, concrete uses.
- Choose readable over clever; optimize only what you've measured.
- Delete dead code, unused options, and speculative parameters.
Don't
- Don't add config, flags, or generality for hypothetical future needs (YAGNI).
- Don't build a framework, factory, or interface for a single implementation.
- Don't add caching, async, queues, or "scalability" without a measured need.
- Don't design for scale you don't have.
- Don't gold-plate — stop when the requirement is met.
Rule of thumb
If you can't point to a concrete, current reason for a piece of complexity, remove it.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.