agentleFS
Sign inStart free
freemtyfreemty/labmate/CLAUDE.md

labmate

CLAUDE.md25 starsChanged 2 months agoMITView on GitHub

Research harness for AI coding agents: 12 portable skills, five Claude named agents, shared references/scripts, and four default hook handlers across four lifecycle events. - Claude Code registers the five named agents from .claude-plugin/plugin.json. Their Markdown bodies must still work as portable role references for Codex fallback. - Deterministic project mutation belongs in scripts/; SKILL.md files remain thin discovery and judgment guides. - Claude explicit-invocation policy lives in skill frontmatter. Codex policy lives in skills/*/agents/openai.yaml. - Package and both plugin…

The file

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not clean storage, reset environments, or interrupt processes while an experiment is active without resolving exact targets and …

    line 20
  2. Distinctive:

    Treat single-machine smoke tests and mock runs as plumbing evidence only.

    line 24

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

LabMate

Research harness for AI coding agents: 12 portable skills, five Claude named agents, shared references/scripts, and four default hook handlers across four lifecycle events.

Non-obvious boundaries

  • Claude Code registers the five named agents from .claude-plugin/plugin.json. Their Markdown bodies must still work as portable role references for Codex fallback.
  • Deterministic project mutation belongs in scripts/; SKILL.md files remain thin discovery and judgment guides.
  • Claude explicit-invocation policy lives in skill frontmatter. Codex policy lives in skills/*/agents/openai.yaml.
  • Package and both plugin manifests share one version. A changed plugin must receive a new version so installed caches cannot alias different source.

Research safety

  • Do not clean storage, reset environments, or interrupt processes while an experiment is active without resolving exact targets and authorization.
  • Preserve successful units during recovery and use the experiment's own success predicate.
  • Treat single-machine smoke tests and mock runs as plumbing evidence only.

Verification

bash tests/test-hooks.sh
bash tests/test-platform-compat.sh
bash tests/test-context-contract.sh
bash tests/test-scripts.sh

Preserve unrelated worktree changes. Commit this nested repository before its parent gitlink.

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