agentleFS
Sign inStart free
nirholasnirholas/three.ws/AGENTS.md

three.ws

AGENTS.md264 starsChanged 43 days agoApache-2.0View on GitHub

Read CLAUDE.md in full before doing anything and follow it exactly. It is the operating rulebook for every agent in this repo, not only Claude. Its hard rules, stop-and-ask gates, commit-message format, $THREE commit gate, and em-dash ban all apply to you. The rules agents break most often:

  • Commits and pushes

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

5 rules. About 0 are common, 2 are distinctive, and 3 are 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read CLAUDE.md in full before doing anything and follow it exactly.

    line 3
  2. Very specific:

    Never git push, deploy, run npm run db:migrate, or sign or send any on-chain transaction.

    line 10
  3. Distinctive:

    Never write the em-dash or en-dash characters anywhere.

    line 11
  4. Very specific:

    Before each commit run npm run check:rules -- --paths <every file you changed> and fix what it reports.

    line 12
  5. Very specific:

    Commit subjects follow type(scope): what changed and why it matters.

    line 13

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

three.ws: rules for Codex and other non-Claude agents

Read CLAUDE.md in full before doing anything and follow it exactly. It is the operating rulebook for every agent in this repo, not only Claude. Its hard rules, stop-and-ask gates, commit-message format, $THREE commit gate, and em-dash ban all apply to you.

The rules agents break most often:

  • Stage explicit paths only. Never git add -A or git add .; other agents share this repo.
  • Never git push, deploy, run npm run db:migrate, or sign or send any on-chain transaction.
  • Never write the em-dash or en-dash characters anywhere. Use a period, comma, colon, or hyphen.
  • Before each commit run npm run check:rules -- --paths <every file you changed> and fix what it reports.
  • Commit subjects follow type(scope): what changed and why it matters. Generic subjects are rejected.

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