Lesson format
Reading lesson with structured written material and clear navigation inside the course flow.
Reading lesson with structured written material and clear navigation inside the course flow.
This lesson is free and open to all visitors.
CLAUDE.md is the identity layer — short, always loaded, rarely changing. But no business fits in 200 lines. Your pricing logic, project templates, client histories, decisions, and patterns need a bigger home. That home needs three properties: local-first, plain text, and link-aware. Obsidian satisfies all three.
This lesson is about why the Obsidian vault — a folder of connected markdown files — is the single most useful external memory layer you can pair with Claude Code today.
Obsidian is a desktop app that reads a local folder of .md files and treats them as a graph. Every file can link to other files using [[wikilinks]]. Every file can have YAML frontmatter for metadata. The graph view shows you the entire knowledge network as nodes and edges.
Crucially for us: the vault is just a folder. Claude Code can read it, grep it, and write to it like any other directory. Obsidian's app is the editor for humans; the folder is the source of truth for the AI.
No API to query, no rate limit, no credentials, no cloud dependency. If the files are on your disk, Claude can read them today. Privacy is default: your business stays in your machine.
Every file is readable without any tool. A client file from 2023 opens in any text editor. This is the opposite of SaaS knowledge bases that lock you in — and it matters for memory that needs to outlive tools.
Links are the superpower. A file can reference another file, and Obsidian maintains that relationship automatically. When Claude reads pricing/landing-saas.md and sees a link to past-projects/acme-corp.md, it can fetch exactly that file — not the whole vault.
Most knowledge bases are organized as folders and subfolders — a tree. Trees force one hierarchy. Your content is more complex than that. A past project belongs to a client, uses a specific stack, has a pricing decision, and teaches a pattern. A tree can only place it in one of those parents.
A graph lets the same node live in all those contexts simultaneously via links. The Codearia project past-projects/acme-saas.md links to clients/acme-corp.md, stack-decisions/tailwind-v4.md, and patterns/hero-animation.md. Claude can enter from any direction and still find it.
Obsidian culture has a concept called an idea garden: notes that grow as you return to them, connecting to more and more other notes. For a business, this translates cleanly:
Writing grows the brain. The graph catches the links.
You could. Your CLAUDE.md would hit 5,000 lines and every Claude Code turn would spend 60,000 tokens just loading it — before you even typed a question. Quality would drop. Cost would explode. Lost-in-the-middle would kick in.
The vault exists precisely so CLAUDE.md can stay small. The pattern is: CLAUDE.md points at the vault, Claude reads only the files it needs for the current question. That is what the next lesson — index-first retrieval — is about.
CLAUDE.md is the front door. Obsidian is the house. Claude walks into the right room as needed — and never has to memorize the whole house at once.