The note-taking-app discourse online tends to make Obsidian sound like a fashion choice — vim-vs-emacs but for typing notes. It isn’t, quite. Obsidian’s value proposition is specific and unusual: instead of organizing notes into folders, you connect them into a graph by wiki-style links, and the graph itself becomes something you can navigate, query, and reason over. Once the graph is there, an LLM that can read across it (Claude is the natural pairing, since the Obsidian Claude plugin shipped in late 2025) turns the whole network into a long-term memory system — a second brain that doesn’t forget what it learned six months ago and can answer “what did I know about X last spring” the same way a colleague would.
This field guide is the plain-English walkthrough. It assumes nothing about your note-taking history — if you currently keep notes in a Google Doc, a Notes.app sidebar, or nowhere at all, this is the on-ramp. The first half is Obsidian itself: links, tags, properties, daily notes, the living graph. The second half is the AI integration that makes the whole thing earn the “second brain” label, plus the dozen workflows that experienced users converge on.
What it covers
Twelve sections, about sixteen minutes of reading.
§ 01 — The one-sentence answer. What Obsidian is. A local-first Markdown editor that turns your notes folder into a navigable knowledge graph.
§ 02 — Folders vs. links — the core shift. The mental model that changes everything. Most note-taking apps make you decide where a note lives. Obsidian lets you decide what it connects to. Why this small change reorganizes the entire experience of having notes.
§ 03 — Try it: the living graph. The graph view. What it looks like, what it’s actually useful for (less than the screenshots suggest, but more than zero), and the small habits that make it grow into something interesting.
§ 04 — Tags vs. links — when to use which. The two cross-referencing mechanisms. Links are for “this note is about that thing.” Tags are for “this note has the property of that thing.” The distinction matters and most beginners mix them up.
§ 05 — Properties — giving notes machine-readable structure. YAML front-matter as the bridge between human-readable notes and machine-readable data. The dozen properties that earn their keep (status, date, project, tags) and the trap of over-structuring.
§ 06 — Daily notes — the easiest habit that works. The one workflow that gets most people from “I downloaded Obsidian” to “I actually use Obsidian.” A daily note as the working scratchpad that catches everything before it filters into long-term notes.
§ 07 — Why “second brain”? The Tiago Forte / Building-a-Second-Brain framing in honest terms. What this metaphor gets right (notes-as-thinking-substrate). What it gets wrong (the productivity-influencer overpromise). What’s left after you subtract the marketing.
§ 08 — Adding Claude: memory + reasoning. The integration that makes the second-brain framing actually work. The Obsidian Claude plugin. What it can do (read across your notes, answer questions grounded in your own writing, help draft new notes that link properly into the existing graph). What it can’t (replace the habit of writing in the first place).
§ 09 — A worked example. Following one project — a small home-electronics build — through the system. The daily notes that captured the work, the linked notes that emerged, the queries that retrieved the right thing six months later.
§ 10 — The plugin ecosystem, briefly. What’s worth installing. Templater. Dataview. The Calendar plugin. The handful that earn their keep, and the eighty that don’t.
§ 11 — Pitfalls. The traps that catch people. Over-structuring before you have notes. Importing every research paper before you’ve written anything. Treating Obsidian as a productivity system instead of as a thinking substrate. The dozen ways to spend a Saturday “setting up Obsidian” without producing a single useful note.
§ 12 — Further reading. The official documentation. The handful of YouTube channels that teach Obsidian without the productivity-influencer overpromise. The Forte book if you want the maximalist version.
Read it
The field guide lives at its own URL with a warm-paper layout — brick-red accent, twelve sections, screenshots throughout. Plain-English explanations, no productivity-influencer hyperbole.
← Back to Autonomy