agentleFS
Sign inStart free
AgriciDanielAgriciDaniel/fablesecondbrain/CLAUDE.md

fablesecondbrain

CLAUDE.md32 starsChanged 4 months agoMITView on GitHub

Claude-specific note: this file is persistent project context, not an enforcement layer. Release readiness is enforced by scripts/audit_brain.py and scripts/package_release.py. Master copy: wiki/meta/CONVENTIONS.md (restore from there if a brainstein upgrade overwrites this file). - Three layers: .raw/ immutable sources with sha256 manifest; wiki/ knowledge; this file the agent contract. Never edit anything under .raw/. - Read order for any session: wiki/hot.md, then wiki/index.md, then the relevant _index.md hub, then the note. - Every wiki page carries flat YAML frontmatter: type,…

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. lovepixel-git/fablesecondbrain★ 0100% 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 repository2 other files it gives its agents.

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read order for any session: wiki/hot.md, then wiki/index.md, then the relevant _index.md hub, then the note.

    line 16
  2. Very specific:

    Every wiki page carries flat YAML frontmatter: type, title, status (seed|developing|mature|evergreen), created, updated, tags, domain, …

    line 18
  3. Very specific:

    Run python3 scripts/lint_vault.py and python3 scripts/audit_brain.py --json before committing.

    line 30

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

Fable 5 Brain Claude Instructions

@AGENTS.md

Claude-specific note: this file is persistent project context, not an enforcement layer. Release readiness is enforced by scripts/audit_brain.py and scripts/package_release.py.

Vault operating contract

Master copy: wiki/meta/CONVENTIONS.md (restore from there if a brainstein upgrade overwrites this file).

  • Three layers: .raw/ immutable sources with sha256 manifest; wiki/ knowledge; this file the agent contract. Never edit anything under .raw/.
  • Read order for any session: wiki/hot.md, then wiki/index.md, then the relevant _index.md hub, then the note.
  • Every wiki page carries flat YAML frontmatter: type, title, status (seed|developing|mature|evergreen), created, updated, tags, domain, confidence, related (>= 6 quoted wikilinks), source_urls, sources. Domains and tags per wiki/meta/Tag Taxonomy.md; confidence per references/CONFIDENCE_TAGS.md.
  • Note bodies: answer-first line, What it is, How it works, Best practice, Pitfalls, Sources (dated), Related (>= 8 wikilinks), Next actions. Export quotes verbatim, at most 15 words, attributed System Prompt Export 2026-07, L<start>-<end>.
  • wiki/log.md append-only newest on top (## [YYYY-MM-DD] operation | Title); wiki/hot.md overwritten, 500 words max; wiki/index.md updated on every change.
  • Filenames Title Case and unique vault-wide; folders lowercase; no em dashes anywhere.
  • Domain claims need a dated source or an export line ref. Never invent model or harness behavior; unknowns get status: seed or a > [!gap] callout.
  • Run python3 scripts/lint_vault.py and python3 scripts/audit_brain.py --json before committing. Do not call this brain market-ready unless the audit gate passes.
  • Local git only; never push without the owner's explicit OK.
  • The global /save rule routes conversation saves to the Second Brain, not this vault.

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