agentleFS
Sign inStart free
Kashyap-001Kashyap-001/second-brain-template/CLAUDE.md

second-brain-template

CLAUDE.md0 starsChanged 4 months agoMITView on GitHub

This is a personal knowledge vault with an AI-agent automation framework layered on top. Before doing anything: See <VAULT_ROOT>/AI-Second-Brain-Blueprint.md for the full architecture. If this vault has a knowledge graph at graphify-out/ (built by the graphify tool — install separately, see README), it has god nodes, community structure, and cross-file relationships. Rules: - For codebase questions, first run graphify query "<question>" when graphify-out/graph.json exists. Use graphify path "<A>" "<B>" for relationships and graphify explain "<concept>" for focused concepts. These return…

The file

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

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

  • 6

    Very specific

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

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

    Read <VAULT_ROOT>/.agents/AGENTS.md for global behavior rules (read-only constraints, self-healing loop, memory routing, token …

    line 5
  2. Very specific:

    Read the relevant mistakes/learnings file before coding, if your domain has one (e.g.

    line 6
  3. Very specific:

    If this vault has a knowledge graph at graphify-out/ (built by the graphify tool — install separately, see README), it has god nodes, …

    line 16
  4. Very specific:

    If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.

    line 20
  5. Very specific:

    Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.

    line 21
  6. Very specific:

    After modifying code, run graphify update .

    line 22

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

Second Brain — AI Agent Rules

This is a personal knowledge vault with an AI-agent automation framework layered on top. Before doing anything:

  1. Read <VAULT_ROOT>/.agents/AGENTS.md for global behavior rules (read-only constraints, self-healing loop, memory routing, token preservation).
  2. Read the relevant mistakes/learnings file before coding, if your domain has one (e.g. Development/Odoo/Odoo-Mistakes.md if you're using the Odoo example skill pack, or Development/General-Mistakes.md for general code).
  3. Save all learnings back to the vault:
    • Domain-specific fixes → use the brain-sync skill
    • General fixes → append to General-Mistakes.md
    • Personal/session notes → append a bullet summary to today's daily log

See <VAULT_ROOT>/AI-Second-Brain-Blueprint.md for the full architecture.

graphify

If this vault has a knowledge graph at graphify-out/ (built by the graphify tool — install separately, see README), it has god nodes, community structure, and cross-file relationships.

Rules:

  • For codebase questions, first run graphify query "<question>" when graphify-out/graph.json exists. Use graphify path "<A>" "<B>" for relationships and graphify explain "<concept>" for focused concepts. These return a scoped subgraph, usually much smaller than a full report or raw grep output.
  • If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.
  • Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.
  • After modifying code, run graphify update . to keep the graph current (AST-only, no API cost).

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