agentleFS
lhotwll217lhotwll217/owner-operator/docs/AGENTS.md

owner-operator

AGENTS.md8 starsChanged 44 days agoMITView on GitHub

This folder is the single home for behavior knowledge. Code, README, and prompts point here; they do not restate. - Every page starts with routing frontmatter. title, a one-line summary, and read_when triggers let a reader or agent pick the right page without reading bodies. The summary says what the page is; read_when alone owns when to read it. - One page per surface. A page owns its surface's behavior; overlapping content merges or points. - Point at in-code contracts…

The file

We split this AGENTS.md into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Write only the current contract: Before saving, ask: what context am I assuming, what code change would falsify this silently, and where …

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md

Docs

This folder is the single home for behavior knowledge. Code, README, and prompts point here; they do not restate.

  • Every page starts with routing frontmatter. title, a one-line summary, and read_when triggers let a reader or agent pick the right page without reading bodies. The summary says what the page is; read_when alone owns when to read it.
  • One page per surface. A page owns its surface's behavior; overlapping content merges or points.
  • Point at in-code contracts instead of restating them. Catalogs, schema docs, and flag parsers document themselves; pages link to them.
  • Write only the current contract. Before saving, ask: what context am I assuming, what code change would falsify this silently, and where else have I already said this?

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.