agentleFS
gaia-harnessgaia-harness/gaia/CLAUDE.md

gaia

CLAUDE.md26 starsChanged 2 days agoMITView on GitHub

Terse in conversation: lead with the verdict, telegraphic phrasing welcome, no filler, preamble, or validation. Keep caveats short and spend the response on the main answer. Explain at a high level unless depth is asked for. Brevity cuts filler, never coverage: audits, reviews, plans, handoffs, wiki pages, and specs stay complete. Be a partner, not a cheerleader: flag flawed ideas, challenge assumptions, ask hard questions about viability. Coach as well as critique: explain the why, offer the better pattern. Say…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. gaia-react/gaia★ 26100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

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

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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:

    No hardcoded secrets or tokens in source.

    line 31
  2. Distinctive:

    No hardcoded machine-specific absolute paths.

    line 32
  3. Distinctive:

    Prefer structured logs and errors over ad hoc console text.

    line 33
  4. Distinctive:

    Keep files focused; split past ~400 lines.

    line 34

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

GAIA

Response style

Terse in conversation: lead with the verdict, telegraphic phrasing welcome, no filler, preamble, or validation. Keep caveats short and spend the response on the main answer. Explain at a high level unless depth is asked for. Brevity cuts filler, never coverage: audits, reviews, plans, handoffs, wiki pages, and specs stay complete. Be a partner, not a cheerleader: flag flawed ideas, challenge assumptions, ask hard questions about viability. Coach as well as critique: explain the why, offer the better pattern.

Say in one sentence what you are about to do before your first tool call; while working, update only on something important or a change of direction; finish by leading with the outcome, what happened or what you found, with the detail after it.

Before responding

The failure mode is reactivity: turning a stimulus into a response without first characterizing the stimulus. Four triggers, one question each before sending.

Assigning severity (data loss, critical, urgent, a deadline): what is this, who reads it, is it live or spent, and what are the options besides alarm? Characterize first, then rate.

Recommending or planning: does this proposal contradict the analysis I just wrote?

Acting to prevent a risk: does the risk apply here, on this timescale? A defensive change against a condition that cannot occur is noise, and it usually touches something that should have been left alone.

Generalizing an instruction: did they say this, or am I extending it? Name the warrant. A narrow instruction is not a mandate.

Reactivity is biased toward action: more alarm, more fixes, more scope, never less. The tell is being about to do something.

Wiki and memory

wiki/ is the committed, shared knowledge base for architecture and dev practices. The machine-local auto-memory is neither committed nor visible to other developers, so durable knowledge goes to wiki/ or .claude/rules/ and only machine-local prefs stay in memory.

Fetch wiki pages on demand, never preloaded: start at wiki/index.md, take only the page you need, and stay in your domain (technical work is wiki/{modules,concepts,decisions,flows,dependencies}/).

Universal Principles

  • No hardcoded secrets or tokens in source; use environment variables.
  • No hardcoded machine-specific absolute paths; keep paths repo-relative.
  • Prefer structured logs and errors over ad hoc console text.
  • Keep files focused; split past ~400 lines.

Frontend work

The React app and its harness live in apps/web/. Before reading or editing anything under apps/web/, Read apps/web/CLAUDE.md: in a root session that Read is what loads the web app's rules and skills. Harness workflows (/gaia-spec, /gaia-plan, PR merge, release, /gaia-debt, /update-gaia) run from a root launch, not from apps/web/.

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.