agentleFS
roronoazoroshao369roronoazoroshao369/vibe-coding-os/skills/prompts/anti-overengineering/SKILL.md

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

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
  1. Distinctive:

    Keep solutions simple, local, and proportional to the request.

    line 16
  2. Distinctive:

    Use when a task tempts architecture astronautics, broad abstractions, or speculative features.

    line 20
  3. Distinctive:

    Prefer existing patterns over new frameworks.

    line 30
  4. Distinctive:

    Leave future ideas as follow-ups, not implementation.

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. State the smallest acceptable solution.
  2. Reject features not required by the spec.
  3. Prefer existing patterns over new frameworks.
  4. Make trade-offs explicit.
  5. 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".

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.