agentleFS
Sign inStart free
neuraforge-cl-esneuraforge-cl-es/adaptive-engineering/skills/simplification-gate/SKILL.md

simplification-gate

Skill1 starsChanged 11 days agoMITView on GitHub

Review an implementation or diff for avoidable complexity, unnecessary code, dependencies, abstractions, configuration, and duplication before completion.

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:

    Treat complexity as a cost that requires evidence.

    line 7
  2. Distinctive:

    Look for code that can be deleted without changing required behavior.

    line 12
  3. Distinctive:

    Look for new code that duplicates repository capabilities.

    line 13
  4. Distinctive:

    Ensure simplification does not hide real domain boundaries or compromise correctness.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Simplification Gate

Treat complexity as a cost that requires evidence.

Review sequence

  1. Compare actual scope with the declared complexity budget.
  2. Look for code that can be deleted without changing required behavior.
  3. Look for new code that duplicates repository capabilities.
  4. Challenge each new dependency, abstraction, interface, service, config key, and persistent field.
  5. Replace clever/general solutions with boring/specific ones when the latter satisfy current requirements.
  6. Ensure simplification does not hide real domain boundaries or compromise correctness.

Findings

Classify findings:

  • REMOVE: no value for current requirements
  • REUSE: existing capability should replace it
  • COLLAPSE: abstraction is premature
  • KEEP: complexity is justified by a concrete boundary or requirement

Apply safe simplifications directly when operating in implementation mode. Otherwise report them with the expected impact.

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.

Check your setup, free