anti-overengineering
Skill1 starsChanged 5 months agoMITView on GitHub
Keep solutions simple, local, and proportional to the request. Use when a task tempts architecture astronautics, broad abstractions, or speculative features. User request, constraints, current design, proposed solution. A simplified approach and trimmed scope. This is the Simplicity-First member of a four-part engineering discipline set: - skills/prompts/karpathy-engineering-discipline/SKILL.md — Think Before Coding and Surgical Changes. - skills/core/goal-driven-execution/SKILL.md — Goal-Driven Execution (imperative → verifiable goal with per-step checks). - skills/core/verification-before-done/SKILL.md — the evidence bar for "done".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- yanzyuyu/min-toktheir own version, first seen Nov 8, 2026
- yueheng-rgb/codex-factorytheir own version, first seen Sep 15, 2026
- DGouron/review-flowtheir own version, first seen May 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- yueheng-rgb/codex-factory★ 100same name
- DGouron/review-flow★ 44same name
- yanzyuyu/min-tok★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository117 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- advanced-orchestrationSkill
- architect-agentSkill
- implementer-agentSkill
- quality-councilSkill
- reviewer-agentSkill
- tester-agentSkill
- writer-critic-pairSkill
- authoring-skillsSkill
- api-endpoint-qualitySkill
- async-job-qualitySkill
- auth-qualitySkill
- db-migration-qualitySkill
- frontend-state-qualitySkill
- acceptance-criteriaSkill
- adaptive-flowSkill
- adaptive-prompt-selectionSkill
- adversarial-code-reviewSkill
- architecture-decision-recordsSkill
- brainstormingSkill
- brownfield-spec-enhancementSkill
- bug-fix-lifecycleSkill
- checkpoint-validationSkill
- cicd-integrationSkill
- clarify-before-codeSkill
- claude-code-hooks-packSkill
- code-context-packSkill
- code-intelligence-reviewSkill
- context-policySkill
- context-rich-implementationSkill
- crash-proof-planningSkill
- critique-pass-protocolSkill
- dependency-aware-task-orderingSkill
- deprecation-migrationSkill
- disciplined-diagnosisSkill
- docs-authorSkill
- executing-plansSkill
- external-skillSkill
- finishing-a-development-branchSkill
- git-guardrailsSkill
- goal-driven-executionSkill
- grill-user-before-buildingSkill
- guard-bypass-protocolSkill
- improve-codebase-architectureSkill
- incremental-reviewSkill
- issue-slicingSkill
- lessons-learned-dbSkill
- loop-engineeringSkill
- model-aware-configSkill
- model-weakness-memorySkill
- multi-repo-learningSkill
- orchestration-workflowsSkill
- plan-driven-executionSkill
- plan-from-specSkill
- prd-from-contextSkill
- project-constitutionSkill
- prompt-architectureSkill
- prototype-before-commitmentSkill
- quality-engineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Keep solutions simple, local, and proportional to the request.
- Distinctive: line 20
Use when a task tempts architecture astronautics, broad abstractions, or speculative features.
- Distinctive: line 30
Prefer existing patterns over new frameworks.
- Distinctive: line 32
Leave future ideas as follow-ups, not implementation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Anti-Overengineering
Purpose
Keep solutions simple, local, and proportional to the request.
When to use
Use when a task tempts architecture astronautics, broad abstractions, or speculative features.
Inputs
User request, constraints, current design, proposed solution.
Workflow
- State the smallest acceptable solution.
- Reject features not required by the spec.
- Prefer existing patterns over new frameworks.
- Make trade-offs explicit.
- Leave future ideas as follow-ups, not implementation.
Outputs
A simplified approach and trimmed scope.
Failure modes
- Under-solving real requirements.
- Using simplicity as an excuse to skip quality.
- Hiding future migration costs.
Verification checklist
- Solution satisfies current acceptance criteria.
- No speculative features were added.
- Complexity is justified.
- Follow-ups are separate.
Related skills
This is the Simplicity-First member of a four-part engineering discipline set:
skills/prompts/karpathy-engineering-discipline/SKILL.md— Think Before Coding and Surgical Changes.skills/core/goal-driven-execution/SKILL.md— Goal-Driven Execution (imperative → verifiable goal with per-step checks).skills/core/verification-before-done/SKILL.md— the evidence bar for "done".
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

