agentleFS
Sign inStart free
selamy-labsselamy-labs/agent-skills/skills/enums-codify-behavior/SKILL.md

enums-codify-behavior

Skill0 starsChanged 4 days agoMITView on GitHub

Use when behavior modes are represented by booleans, strings, or repeated conditionals. Prefer enums or tagged unions with behavior per case.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when a mode, command, status, or option controls behavior in multiple places.

    line 8
  2. Distinctive:

    Test every behavior case and at least one invalid input.

    line 20
  3. Very specific:

    Prefer an enum option such as --mode=check|fix|report over boolean flags like --fix and --report when options can conflict or grow.

    line 24

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

Enums Codify Behavior

Use this skill when a mode, command, status, or option controls behavior in multiple places.

Workflow

  1. Name the behavior cases as an enum, literal union, sealed class, or equivalent native construct.
  2. Replace boolean flags when the name does not fully explain the behavior or future cases are plausible.
  3. Move behavior close to the enum case through methods, pattern matching, dispatch tables, or exhaustive switches.
  4. Make unknown or unsupported values fail with a clear error at the boundary.
  5. Test every behavior case and at least one invalid input.

CLI Rule

Prefer an enum option such as --mode=check|fix|report over boolean flags like --fix and --report when options can conflict or grow. Boolean flags are fine for a single independent yes/no setting.

Review Checks

  • The enum name describes the behavior, not just the transport value.
  • Exhaustiveness is checked by the compiler, type checker, linter, or tests.
  • String parsing is limited to input boundaries.
  • Adding a case creates a visible compiler, linter, or test failure until the behavior is implemented.

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