In the first article, I wrote that Karpathy’s second brain is not magic. It is a folder that gets smarter.
This piece is the continuation.
If you have not read the first one, read that first. That article explains the shift. This one explains the desk setup, the moving parts, the prompts, and the habits that make the whole thing useful.
Because the truth is simple: the idea sounds smart on day one, but the real value comes from what happens after you open Obsidian, point Claude Code at the vault, and start using it like a real system instead of a cool demo.
Karpathy’s gist calls this an LLM Wiki: an idea file you can paste into your own agent so it builds the setup around your needs, not his. Claude Code’s docs add the missing operational layer with CLAUDE.md
, skills, hooks, and project memory. Obsidian gives you the local markdown workspace, and Web Clipper gives you a fast way to feed it.
The first article was the map. This one is the keyboard.
The first article was about the idea: collect raw material, let the LLM compile a wiki, then ask better questions against that wiki.
This article is narrower.
It is about why Claude Code and Obsidian fit this pattern so well together.
Obsidian is where you see the knowledge. Claude Code is what keeps working on it. CLAUDE.md
is where you write the standing rules. Skills are where you put repeatable playbooks. Web Clipper is how you keep feeding the system without friction. Marp is how you turn your notes into something presentable when needed.
And that is the practical jump from article one to article two:
not just a second brain as a concept, but a second brain with an actual workflow.
Give one vault one job
Most people ruin this setup by trying to make one vault hold everything.
Work, life, half-read articles, random screenshots, voice notes, recipe ideas, startup plans, course notes, all in one place.
That sounds efficient. It usually becomes noise.
Start with one vault for one serious theme.
Good examples:
your AI research and writing
one business or client niche
one course or degree subject
one market you are studying
one product or project you are building
Karpathy’s own pattern is domain-shaped, not “store my whole life in one giant bucket.” The attached drafts were right to keep repeating that focused knowledge bases work better because they create cleaner links, better synthesis, and fewer stupid collisions.
Subscribe now
Inside the full article: the exact setup, smarter structure, the upgraded vault structure, Claude Code rules, Clipper flow, Skills, prompts, outputs, weekly workflow, MCP, cleanup system, Obsidian reading flow, hooks, subagents, and the advanced layers that make the whole thing actually work.
Read more
