agentleFS
Sign inStart free
gh-xjgh-xj/agent-repo-kit/CLAUDE.md

agent-repo-kit

CLAUDE.md0 starsChanged 6 months agoMITView on GitHub

You are inside agent-repo-kit. This repo publishes a convention for other repos to adopt, and it also adopts that same convention on itself — task verify runs here. Before changing conventions, persistent state models, agent workflows, or repo-wide architecture, read docs/core-belief.md. It is the philosophical north star for this repo; this file is the operational map. See AGENTS.md for the canonical entry-points map and the rules for editing the kit-owned surfaces (skills/, adapters/<harness>/). This file mirrors AGENTS.md; keep both in…

  • Installs packages

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Before changing conventions, persistent state models, agent workflows, or repo-wide architecture, read docs/core-belief.md.

    line 9

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

CLAUDE.md — agent-repo-kit

You are inside agent-repo-kit. This repo publishes a convention for other repos to adopt, and it also adopts that same convention on itself — task verify runs here.

Core belief

Before changing conventions, persistent state models, agent workflows, or repo-wide architecture, read docs/core-belief.md. It is the philosophical north star for this repo; this file is the operational map.

See AGENTS.md for the canonical entry-points map and the rules for editing the kit-owned surfaces (skills/, adapters/<harness>/). This file mirrors AGENTS.md; keep both in sync by hand.

The work CLI now lives in its own repo: https://github.com/gh-xj/work-cli. The work-cli-qa skill (the source-side release gate) moved with it. ARK keeps the work-cli skill — the operator-facing playbook — and the adapter mirrors. ARK's task verify installs the external work binary (or hard-fails) and asserts min_work_version from .conventions.yaml.

Conventions

  • Docs — tracked repo docs live under docs/ using the requests/, planning/, plans/, implementation/, and taxonomy/ folders.
  • Work — local-first work tracker at .work/. The CLI is the external work-cli; install with go install github.com/gh-xj/work-cli/cmd/work@latest (or via the release tarball). Drive it through task work -- .... Local state lives in the ignored .work/config.yaml and .work/items/*.yaml. Daily commands: task work -- inbox, task work -- inbox add "title", task work -- triage accept IN-0001, task work -- view ready, and task work -- show W-0001.
  • Conventions descriptor — .conventions.yaml at the repo root declares which conventions this repo opts into, including min_work_version for the external work CLI. Read by the convention-engineering skill for bootstrap and audit; enforced by scripts/verify.sh.

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