agentleFS
Sign inStart free
zarubinvibezarubinvibe/zeuz/AGENTS.md

zeuz

AGENTS.md2 starsChanged 3 months agoMITView on GitHub

The smoke test must end with ГЕЙТ ПРОЙДЕН ✓. Review the diff before handoff. - README.md and README.ru.md follow the shared family anatomy: promise, badges, wide hero, table of contents, and the ten beginner headings with the ASCII workflow diagram inside How It Works. - Workflow stages live in .github/pantheon.json. Change the stages there first, then the two READMEs. - AGENTS.md holds the rules; CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, and .cursor/rules/*.mdc only point here. - Run public-repo-gate check --repo . --release-intent public…

  • 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 31,774 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 repository5 other files it gives its agents.

The file

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

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

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Keep changes inside this repository.

    line 12
  2. Very specific:

    Treat workflows/zeuz-pipeline.js as host-executed source, not a standalone Node program.

    line 13
  3. Very specific:

    Keep runtime output under runs/.

    line 15
  4. Common:

    Do not add secrets, credentials, machine-specific absolute paths, sessions, caches, or private runtime state.

    line 16
  5. Very specific:

    When pipeline phases or required outputs change, update specs/00-roadmap.md and rules/best-practices.md in the same patch.

    line 20
  6. Very specific:

    Keep CLAUDE.md as a short router.

    line 21
  7. Distinctive:

    Put irreversible file, archive, publish, move, and deployment actions behind explicit host approval.

    line 23
  8. Very specific:

    Run public-repo-gate check --repo .

    line 42

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

Agent guide

Read first

  1. CLAUDE.md
  2. rules/best-practices.md
  3. specs/00-roadmap.md
  4. Relevant files under agents/ and docs/decisions/

Scope

  • Keep changes inside this repository.
  • Treat workflows/zeuz-pipeline.js as host-executed source, not a standalone Node program.
  • Preserve the six checked-in specialist roles unless a task explicitly changes the factory design.
  • Keep runtime output under runs/; never track it.
  • Do not add secrets, credentials, machine-specific absolute paths, sessions, caches, or private runtime state.

Change rules

  • When pipeline phases or required outputs change, update specs/00-roadmap.md and rules/best-practices.md in the same patch.
  • Keep CLAUDE.md as a short router. Put detail in rules/, specs/, or docs/.
  • Describe host requirements and limitations directly. Do not claim a full end-to-end run from the static smoke test.
  • Put irreversible file, archive, publish, move, and deployment actions behind explicit host approval.
  • Preserve English README.md, Russian README.ru.md, attribution, and MIT licensing.

Checks

bash smoke/smoke.sh
git diff --check

The smoke test must end with ГЕЙТ ПРОЙДЕН ✓. Review the diff before handoff.

Public packaging

  • README.md and README.ru.md follow the shared family anatomy: promise, badges, wide hero, table of contents, and the ten beginner headings with the ASCII workflow diagram inside How It Works.
  • Workflow stages live in .github/pantheon.json. Change the stages there first, then the two READMEs.
  • AGENTS.md holds the rules; CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, and .cursor/rules/*.mdc only point here.
  • Run public-repo-gate check --repo . --release-intent public before any push, and fix every blocker.
  • Agent work here is tracked by Entire, and its checkpoints go to the separate private repository zarubinvibe/zeuz-checkpoints. Session capture stays on: a public repository never stores its own checkpoints, and the release gate blocks a push when tracking is disabled or the checkpoint repository is public.

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