agentleFS
appautomatonappautomaton/delineate/AGENTS.md

delineate

AGENTS.md3 starsChanged 30 days agoMITView on GitHub

Open a worktree and a branch for each piece of work, so main always holds what is live: git worktree add .claude/worktrees/<name> -b <name> When the work is done, fast-forward main to the branch in the main checkout and push main from there. Once the push has published the site, remove the worktree and delete the branch (git worktree remove, git branch -d). Locally, main is the only branch left between pieces of work. The pre-push hook (.githooks/pre-push, which npm…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

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:

    When the work is done, fast-forward main to the branch in the main checkout and push main from there.

    line 9

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

Working on delineate

Each piece of work gets a worktree

Open a worktree and a branch for each piece of work, so main always holds what is live:

git worktree add .claude/worktrees/<name> -b <name>

When the work is done, fast-forward main to the branch in the main checkout and push main from there. Once the push has published the site, remove the worktree and delete the branch (git worktree remove, git branch -d). Locally, main is the only branch left between pieces of work.

Pushing main publishes the site

The pre-push hook (.githooks/pre-push, which npm install turns on) builds the site from the checkout and publishes it to gh-pages before main goes up. Merging is therefore releasing: before main moves, run npm run check and look at the work in a browser, the way its audience will meet it. The hook builds what is committed, so push from a clean checkout whose HEAD is the main being pushed.

Skills

The skills in .agents/skills/ hold how each work is made and what done means for it. Before changing a work, load its skill, and keep the skill true to the code when the code changes. A new style starts as a skill, and the work is drawn from it.

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.