agentleFS
Sign inStart free
jaydubya818jaydubya818/Agentic-Pi-Harness/CLAUDE.md

Agentic-Pi-Harness

CLAUDE.md2 starsChanged 7 months agoMITView on GitHub

Default concise-response mode in this repo: Caveman lite. Use these defaults unless the user asks for more detail: Do not compress away important details for: - governed execution behavior - KB/Wiki policy boundaries - contract/state/event semantics - safety constraints - migration or operational steps - exact commands, paths, IDs, schemas, or failure modes If the user explicitly asks for a detailed explanation, fuller reasoning, or formal wording, expand as needed.

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:

    Default concise-response mode in this repo: Caveman lite.

    line 3
  2. Distinctive:

    Use these defaults unless the user asks for more detail:

    line 5
  3. Distinctive:

    Do not compress away important details for:

    line 12
  4. Distinctive:

    If the user explicitly asks for a detailed explanation, fuller reasoning, or formal wording, expand as needed.

    line 20

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

Claude Code defaults for this repo

Default concise-response mode in this repo: Caveman lite.

Use these defaults unless the user asks for more detail:

  • Normal repo responses: concise, clear, technically exact, low-fluff
  • Code review comments: caveman-review style — one-line findings with severity, problem, fix
  • Commit message suggestions: caveman-commit style — Conventional Commits, terse subject, why over what
  • General engineering work: compress wording, not substance

Do not compress away important details for:

  • governed execution behavior
  • KB/Wiki policy boundaries
  • contract/state/event semantics
  • safety constraints
  • migration or operational steps
  • exact commands, paths, IDs, schemas, or failure modes

If the user explicitly asks for a detailed explanation, fuller reasoning, or formal wording, expand as needed.

Download now (ZIP)

  • In this repositoryOne other file 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.

Reviews can't be read right now.

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