Keep It Simple
Before adding abstraction, asks "do we need this now?" Activates when proposing factories, abstract classes, config-driven behavior, or "for future extensibility." Resists over-engineering. Three similar lines are better than a premature abstraction.
Install
npx skills add ElliotJLT/Claude-Skill-Potions --skill keep-it-simplegit clone --depth 1 https://github.com/ElliotJLT/Claude-Skill-Potions.git /tmp/Claude-Skill-Potions
mkdir -p ~/.claude/skills
cp -r /tmp/Claude-Skill-Potions/skills/keep-it-simple ~/.claude/skills/keep-it-simplePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Keep It Simple <purpose> Claude loves elegant abstractions. User asks for a button, Claude builds a component factory with theming support. The problem: abstractions have costs. They obscure intent, add indirection, and often solve problems that never materialize. This skill enforces YAGNI - You Aren't Gonna Need It. </purpose> ## When To Activate <triggers> - About to create a factory, builder, or abstract base class - Proposing a config-driven solution - Using phrases like "for flexibility" or "in case we need" - Creating a utility for something done twice - Adding parameters "for future use" - Building infrastructure before the feature </triggers> ## Instructions ### The YAGNI Test Before adding abstraction, answer honestly: ```markdown ## Complexity Check **I want to add:** [describe the abstraction] **Because:** [your justification] **Is this solving a problem we have TODAY?** - [ ] Yes, we have 3+ concrete cases now - [ ] No, but we might need it later **If "might need later":** Don't build it. Stop. ``` ### The Rule of Three Abstract when you have **three concrete cases**, not before: | Situation | Action | |-----------|--------| | 1 case | Just write it | | 2 cases | Copy-paste is fine. Note the duplication. | | 3 cases | Now consider abstracting |
Details
- Skill name
keep-it-simple- Repository
- ElliotJLT/Claude-Skill-Potions
- Path
skills/keep-it-simple/SKILL.md- License
- MIT
- Repo updated
- 12 February 2026
FAQ
What does the Keep It Simple skill do?
Before adding abstraction, asks "do we need this now?" Activates when proposing factories, abstract classes, config-driven behavior, or "for future extensibility." Resists over-engineering. Three similar lines are better than a premature abstraction.
How do I install the Keep It Simple skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ElliotJLT/Claude-Skill-Potions --skill keep-it-simple. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Keep It Simple popular?
It lives in ElliotJLT/Claude-Skill-Potions, which has 62 GitHub stars and 2 forks.
Related skills
Agent Audit
62ElliotJLT/Claude-Skill-Potions
When reviewing, optimizing, or inheriting an LLM agent, systematically identify what's actually load-bearing vs. cruft. Instruments usage, ablates components, and strips the agent to minimum viable form. Answers: "What can we remove without degrading quality?" The goal is the leanest agent that still works.
Battle Plan
62ElliotJLT/Claude-Skill-Potions
Before ANY significant development task (new feature, refactor, integration, migration), run a complete planning ritual by orchestrating other skills in sequence: rubber-duck (clarify scope) -> pre-mortem (assess risks) -> eta (estimate time) -> final confirmation. Do not start coding until the battle plan is approved.
Breadcrumbs
62ElliotJLT/Claude-Skill-Potions
Leaves notes for future Claude sessions in .claude/breadcrumbs.md. At session end or after significant work, records what was tried, what worked, what failed, and context for next time. On session start, reads breadcrumbs to understand history. Session-to-session memory without manual updates.
Sketch Checker
38sam-dumont/claude-skills
Use when the user asks to check if a band is sketch, fascist, NSBM, or far-right. Also trigger for: "is [band] sketch?", "is [band] safe?", "sketch check [band]", "check [band] for fascist ties", "is [band] NSBM?", "is [band] fash?", "should I listen to [band]?", "is [band] problematic?", "are [band] nazis?", "RABM check", "band vetting", "is it sketch", "sketch report", "any red flags for [band]", "does [band] have far-right connections", "sketch check", "vet this band", "is [band] safe to support".
Executing Plans
43obra/clank
Execute detailed plans in batches with review checkpoints
Collecting Worker Results
33okgrit/done-is-a-claim
Inspect a stopped worker's returned work and evidence before accepting it, retrying it or handing it to an integration owner. Use when a worker finishes, records disagree, or a green result has no visible change. Collection does not authorize merging.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.