agentleFS
OvichOvich/charrette/skills/guides/guide-complexity/SKILL.md

guide-complexity

Skill14 starsChanged 4 days agoMITView on GitHub

Use when code is written or changed that branches heavily, in any language: if/else or switch chains, type-check cascades, kind fields compared to strings, flag parameters, deep nesting. Produces the branching shaped before it lands, and the bar it must meet at merge. Not for auditing or reworking existing code (complexity-rework).

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Before writing the branch, name what varies: the kinds, the cases.

    line 12
  2. Distinctive:

    Put each case behind one shape: a table, a map of handlers, a type per kind, one function per flag value.

    line 13
  3. Distinctive:

    Keep each function one level of decision.

    line 14
  4. Distinctive:

    No new chain of more than three conditions on the same value.

    line 19
  5. Distinctive:

    No kind compared to strings in more than one place.

    line 20

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

Guide: complexity

Applies to any code that adds or grows branching: a chain of conditions, a dispatch on a kind, a flag that changes what a function does, nesting past two levels.

Shaping step

  1. Before writing the branch, name what varies: the kinds, the cases.
  2. Put each case behind one shape: a table, a map of handlers, a type per kind, one function per flag value.
  3. Keep each function one level of decision; extract the rest.
  4. The branching already exists and is to be reworked: run the complexity-rework skill.

Ok at merge

  • No new chain of more than three conditions on the same value.
  • No kind compared to strings in more than one place; no boolean flag parameter.
  • Nesting at most two levels in the changed code.

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.