agentleFS
Sign inStart free
LegionForgeLegionForge/convobox/CLAUDE.md

convobox

CLAUDE.md2 starsChanged 3 days agoMITView on GitHub

Follow the working agreements in AGENTS.md — they bind every agent in this repo and each rule cites the live incident that created it. Repo orientation: README.md (architecture + status), docs/UAT-checklist.md (live findings, [E]/[L]/[U*] numbering — check existing numbers before adding), docs/KNOWN-ISSUES.md (diagnosed-and-deferred, incl. upstream opencode limitations), docs/AI-ATTRIBUTION.md (attribution convention). Once per clone: git config core.hooksPath .githooks (enables the pre-push privacy scrub that scans outgoing COMMITS, not just the tree). Verification bar: this project's standard is verify-against-the-real-thing — run the…

We split this CLAUDE.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:

    Follow the working agreements in AGENTS.md — they bind every agent in this repo and each rule cites the live incident that created it.

    line 3

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

ConvoBox — Claude Code project instructions

Follow the working agreements in AGENTS.md — they bind every agent in this repo and each rule cites the live incident that created it.

Repo orientation: README.md (architecture + status), docs/UAT-checklist.md (live findings, [E*]/[L*]/[U*] numbering — check existing numbers before adding), docs/KNOWN-ISSUES.md (diagnosed-and-deferred, incl. upstream opencode limitations), docs/AI-ATTRIBUTION.md (attribution convention).

Once per clone: git config core.hooksPath .githooks (enables the pre-push privacy scrub that scans outgoing COMMITS, not just the tree).

Verification bar: this project's standard is verify-against-the-real-thing — run the actual pipeline (audio, STT, backend) rather than trusting unit tests alone, and say plainly which claims are live-verified vs schema-verified.

Download now (ZIP)

  • In this repository2 other files it gives its agents.

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