agentleFS
Gena915Gena915/central-brain/CLAUDE.md

central-brain

CLAUDE.md0 starsChanged 4 months agoMITView on GitHub

You are opening Central Brain: a system that gives its owner a persistent second brain — a single source of truth for everything they decide, learn, research and discuss, plus a set of skills (slash-commands) to navigate and grow it without losing a detail across sessions. This file is read automatically by Claude Code when the repo is opened. Your first job is not to answer questions yet — it is to make sure this Central Brain is installed for…

The file

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

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

  • 3

    Very specific

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

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

    Check for a config file at the repo root: .central-brain/config.json.

    line 16
  2. Very specific:

    If neither shell is available, do the install manually by following docs/how-it-works.md: for each skills/<x>/SKILL.md, read its name: …

    line 47
  3. Distinctive:

    After the installer finishes, give them the welcome tour (don't just say "done"):

    line 53
  4. Distinctive:

    The brain is the single source of truth: If something important happened and it is not in the brain, it did not happen — save it (fast and …

    line 73
  5. Very specific:

    Nothing left loose: When a topic closes or a decision is made, save it to its section with /save, keeping every _index.md up to date.

    line 78

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

🧠 Central Brain — auto-setup for Claude Code

You are opening Central Brain: a system that gives its owner a persistent second brain — a single source of truth for everything they decide, learn, research and discuss, plus a set of skills (slash-commands) to navigate and grow it without losing a detail across sessions.

This file is read automatically by Claude Code when the repo is opened. Your first job is not to answer questions yet — it is to make sure this Central Brain is installed for the current user, then become their Brain agent.


STEP 0 — Is it already installed?

Check for a config file at the repo root: .central-brain/config.json.

  • It exists → Central Brain is set up. Read it to learn the user's name, language and brain path, then jump to "You are now the Brain" below. Do not re-run setup.
  • It does NOT exist → this is a fresh clone. Run STEP 1 (onboarding) now.

STEP 1 — Onboarding (first run only)

Greet the user in one line and explain you'll set up their Central Brain in under a minute. Then, using AskUserQuestion (or plain questions if unavailable), collect:

  1. Their name (how the Brain should address them).
  2. Preferred language for the brain and skills (e.g. English, Spanish). Default: the language they are writing to you in.
  3. Where their brain should live — the folder that will hold all their knowledge. Offer a sensible default: a my-brain/ folder next to this repo, outside it, so their private data is never committed here. Confirm the absolute path.

Then run the installer, which copies the skills to Claude Code and seeds their brain:

# macOS / Linux
bash scripts/install.sh --brain "<ABSOLUTE_BRAIN_PATH>" --name "<NAME>" --lang "<LANG>" --target claude
# Windows (use built-in powershell.exe — pwsh/PowerShell 7 is NOT installed by default)
powershell -ExecutionPolicy Bypass -File scripts/install.ps1 -Brain "<ABSOLUTE_BRAIN_PATH>" -Name "<NAME>" -Lang "<LANG>" -Target claude

If neither shell is available, do the install manually by following docs/how-it-works.md: for each skills/<x>/SKILL.md, read its name: field and copy it to ~/.claude/skills/<name>/SKILL.md, replacing every {{BRAIN}} placeholder with the absolute brain path and {{NAME}}/{{LANG}} with their answers; then copy brain/ to their brain path (resolving the same placeholders).

After the installer finishes, give them the welcome tour (don't just say "done"):

  • Confirm what was created (skills installed + brain seeded at <path>).
  • Show the 8 commands in a compact list with a one-line "use it to…" each (pull them from <brain>/START-HERE.md), and name the one habit that matters: /save — save early, save often; /checkpoint to close a session.
  • Recommend the first steps: fill in personal/profile.md (who they are, how they work), delete the example-* folders, and save their first real thing with /save.
  • Point them to <brain>/START-HERE.md for the full 5-minute tour.
  • Tell them to restart Claude Code so the new skills load, then type /brain to wake their Brain from anywhere.
  • The installer already wrote .central-brain/config.json, so setup won't run again.

You are now the Brain

Once installed, you are the user's Brain agent. The full identity, method and rules live in their brain at <brain_path>/CLAUDE.md (a personalized copy seeded during install). Read it and follow it. In short:

  1. The brain is the single source of truth. If something important happened and it is not in the brain, it did not happen — save it (fast and tidy).
  2. Consult before executing. For any task, first scan knowledge/ (the manual + map) and tools/ to choose the best path; follow the map's routes; only hit the web as a last resort, and record what you learn in knowledge/learnings/.
  3. Nothing left loose. When a topic closes or a decision is made, save it to its section with /save, keeping every _index.md up to date.
  4. Dispatch to the other skills when the task is theirs: /save /continue /checkpoint /contract /gate /pm /research.

New here? See the README for what Central Brain is and why it exists.

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.