How to actually live in an Obsidian vault

Most people install Obsidian, set up four folders, and watch the vault rot. The captures pile up. The inbox crosses 40 files. Notes stop linking to each other. Within a month, opening Obsidian feels like a chore — and the vault stops earning the time it costs.

The fix isn't more folders or a smarter tag taxonomy. It's a working loop: capture cheaply, link liberally, let synthesis happen on its own time, crystallize manually when it matters. This post walks through how to actually live inside an Obsidian vault — folder rules, naming, daily routine, the shortcuts that earn their keep, and the anti-patterns that quietly kill it.

The mental model in one paragraph

The vault is your long-term memory. Folders aren't categories; they're answers to a single question: what is this for? If you can't answer that in 30 seconds, the file belongs in the inbox or the trash. Capture → ground → execute → crystallize is the whole loop. Capture goes into daily-notes/ or inbox/. Ground happens when you re-read or feed material to a tool that synthesizes with citations. Execute is when you actually use the synthesis to do the work. Crystallize is when you, manually, write a permanent note in your own voice. Skip crystallization and the vault becomes a search engine for your own LLM drafts. That's not a second brain. That's a graveyard.

Where things actually go

Six destinations, one decision tree.

daily-notes/ — the capture surface. One file per day, named YYYY-MM-DD.md. Quick captures, meeting fragments, the running thread of what you're thinking about today. Link out, don't dump deep work here. A daily note that's grown to 800 lines means you should have promoted half of it.

inbox/ — the triage zone. Anything captured but not yet decided about. The seven-day rule is the back-pressure that forces processing. Every file in inbox/ gets one of four answers: it has a defined outcome (→ project), it's a topic worth understanding deeply (→ research), it's about a person (→ people), or you don't care anymore (→ delete). If you can't decide in 30 seconds, leave it for next week's review. By week three, indecision converts to deletion.

projects/ — active work with a defined outcome. The defining trait: there's a thing you're trying to finish. A blog post. A side app. A trip plan. If you can't articulate "done looks like X", it's not a project — it's a research topic or a daily-note thread. Each project gets projects/<slug>/ with a one-paragraph README.md describing the outcome.

research/ — long-form synthesized outputs. A topic gets its own folder with analysis.md, sources.md, and optionally deliverables/ and raw/. The line that confuses everyone: a project produces a thing in the world; research produces understanding. "Build a dashboard for X" is a project. "Understand how Singapore startups raise their first round" is research. If your research keeps generating action items, those become projects that cite the research.

Vault root — evergreen permanent notes. Concept notes, principles, reusable templates. Keep this list short.

The condensed decision tree:

Has a date dimension and is fragmentary? → daily-notes/
Need to think about it later? → inbox/
Has a defined outcome? → projects/
Want to understand a topic deeply? → research/
A durable concept you'll reference often? → vault root
None of the above? → delete

Most things should end up in daily-notes/ or get deleted. That's healthy.

Naming rules that aren't aesthetic

The rules read like personal taste. They aren't. Spaces in filenames break shell commands and force quoting. Mixed case fights Cmd + O quick-switch — you don't want to remember whether you wrote "OAuth" or "oauth". Emojis render inconsistently across editors and break terminal commands. Consistency makes the graph view readable.

The non-negotiables:

Slugs are lowercase and hyphenated. agentic-rag-patterns.md, not Agentic RAG Patterns.md and not agentic_rag_patterns.md.
No spaces, ever. Hyphens only. Single most common cause of broken wikilinks.
_ is a reserved sigil. _template.md, _archive-2026-04/, _draft-foo.md. The leading underscore sorts to the top of folder listings and signals "not a real note" at a glance.
No emojis in filenames. They render inconsistently and wreck Cmd + O matching.
Daily notes use whatever date format you're comfortable with — but pick one and never mix. YYYY-MM-DD.md is the default for a reason: it sorts lexicographically in the filesystem and in Cmd + O, and it's unambiguous across regions (no 03/04/2026 guessing game). If you prefer DD-MM-YYYY or MMM-D-YYYY, that's fine — Obsidian's Daily Notes plugin takes any moment.js format. The rule isn't ISO 8601. The rule is consistency. Mixing formats inside one vault is what wrecks sorting and search.

For frontmatter, pick an order — title:, date:, tags:, custom — and stick to it. Use lowercase hyphenated tags as a YAML list (tags: [pkm, obsidian]), not space-separated. Use [[wikilinks]] for vault-internal references, not relative markdown paths — wikilinks survive renames; paths don't. External URLs use standard markdown.

A sheet of paper falling from above splits into five glowing trails, each landing in one of five labeled folders on a cream surface, with a faded trash silhouette to the side. — Every captured note answers one question — what is this for?

A daily-driver routine

Three small habits. They compound.

Morning — orient. Cmd + P, type "daily", run "Daily notes: Open today's daily note". The note opens or gets created from a template (Settings → Daily notes → set the template path). Type your one big thing for the day at the top. Don't over-engineer this. The daily note is a scratchpad, not a system.

During the day — capture without ceremony. Anything you want to remember goes into inbox/ as YYYY-MM-DD-short-slug.md. No frontmatter required. No tags required. Just title and content. The whole point of the inbox is zero friction at capture time and ruthless deletion at triage time.

End of day — close loops. A two-minute habit: re-open today's daily note, write a single line under ## Tomorrow: for the one thing you want to pick up first. That single line is the most reliable handoff mechanism there is. More reliable than any slash command. More reliable than any "wrap-up" prompt.

Weekly — a real review, not a fake one. Once a week, open the last seven daily notes side-by-side. Ask which thread is worth promoting. A thread you've come back to three days in a row is asking to become a project. Create the folder, write a one-paragraph README.md, link the source daily-notes from it. Empty inbox/ aggressively — anything older than seven days that you haven't touched gets archived or deleted. Inbox bankruptcy is real, and the cure is ruthless deletion.

The shortcuts that earn their keep are smaller than you'd guess. Cmd + P is the entry point to everything — every plugin command, every core feature. Cmd + O opens the quick switcher. Cmd + Shift + F is global vault search. Cmd + Click on a [[wikilink]] opens the linked note in a new pane. Typing [[ mid-sentence to start a wikilink with autocomplete is the single highest-leverage habit in Obsidian. Don't aspire to perfect taxonomy; just link liberally. The graph view earns its keep only after weeks of that. Toggle the right sidebar for Backlinks and Outgoing links — this is how you discover that something you wrote three months ago is relevant to what you're doing now.

Plugins worth installing

Obsidian ships lean on purpose — editor, graph, search, backlinks. Community plugins fill the rest. Settings → Community plugins → turn on → Browse → search → Install → Enable. They're sandboxed JavaScript; read the README before enabling something obscure, and don't install plugins you can't articulate a use for.

The short list, in order of how often you'll actually reach for it:

Dataview — turns the vault into a queryable database. Write TABLE, LIST, or TASK queries against frontmatter and tags. Indispensable once projects and research carry real frontmatter.
Templater — programmable templates. Auto-populate today's daily note with date stamps, prompts, and small JS snippets. Pair with the daily-note workflow above so morning capture takes zero thought.
Periodic Notes — daily, weekly, monthly notes from one config. Replaces the core Daily Notes plugin once you start running real weekly reviews.
Calendar — sidebar calendar that highlights dates with notes. Click to jump, miss a day and it shows. Trivial to install, surprisingly load-bearing.
Tasks — checkbox tasks with due dates, recurrence, and queries. Better than re-inventing a TODO system in plain text.
Obsidian Git — auto-commits the vault and pushes to a remote on a schedule. The least-glamorous, most-important plugin the moment the vault is worth losing sleep over.
Excalidraw — embeddable hand-drawn sketches as .excalidraw.md files. Useful when a paragraph needs a diagram and you don't want to leave the vault.

A reasonable starter set is Dataview + Templater + Periodic Notes + Obsidian Git. Add Tasks, Calendar, and Excalidraw when you actually need them — every plugin is something that can break on the next Obsidian update. Browse the full directory at obsidian.md/plugins when a real gap shows up.

Graph view and canvas

Two features worth knowing because they get confused for each other.

The graph view is automatic. Cmd + P → "Graph view: Open graph view" opens the global graph — every note as a node, every wikilink as an edge. It's a vanity metric until the vault is dense enough to show real clusters. The local graph (Cmd + P → "Graph view: Open local graph") is the useful one — pin it in a sidebar, and as you navigate, it shows the neighborhood of whatever note you have open. That's how you discover that today's question connects to something you wrote three months ago.

The canvas is manual. Cmd + P → "Canvas: Create new canvas" makes a .canvas file — an infinite spatial board where you drop notes, images, web embeds, and arrows between them. Use it for anything that resists linear writing: scoping a project, mapping a dependency tree, sketching a research question across sources. The canvas is not a knowledge graph. It's a thinking surface. Save it inside the project or research folder it belongs to and link back from the relevant note. Canvas content doesn't show up in graph view — it isn't indexed the same way.

A bright amber node at the center of a dark navy field, surrounded by a dozen smaller dots connected by thin luminous lines fading into the surrounding darkness. — The local graph, three months in — the neighborhood around whatever note you have open.

Querying your own vault

After three months, the vault becomes a queryable archive of your own thinking. Three layers, in order of how often to reach for them.

Obsidian-native, no AI. If you remember roughly what you wrote, Cmd + Shift + F plus backlinks gets you there in under a minute. For structured queries — "all notes tagged #project that mention X" — install the Dataview plugin and write a small TABLE or LIST query. Dataview turns the vault into a database. Spend an hour learning it once.

An LLM that reads the vault. When you don't remember what you wrote, or you want synthesis across files, point a vault-aware tool at a folder and ask for a citable answer. "Search my vault for everything I've written about X. Group by folder, summarize themes, link back with [[wikilinks]]." Push back if it isn't citing: "Quote the exact sentence and link the file."

Grounded retrieval at scale. When the corpus is too large for one model's context — 300 daily notes, a 200-page PDF — hand it off to a tool like NotebookLM. The output is grounded with inline citations to the exact source chunk. Use this when you need verifiable synthesis, not when you want a quick chat.

To surface forgotten work, ask: "Find orphaned notes (no incoming links, no outgoing links) in research/ and projects/. For each, give me one sentence on what it's about." Orphans are usually either dead ends or buried gold. You have to look to know.

The anti-patterns

These quietly kill the vault.

Letting any tool rename files via raw shell commands. Obsidian only updates wikilinks when files move inside Obsidian. A bare mv old.md new.md from the terminal silently breaks every link. Either rename inside Obsidian, or follow up with a "fix all broken wikilinks" pass afterward.

Letting an AI write directly into your permanent notes. Your authentic voice gets diluted into LLM phrasing within a month. Put AI outputs in their own zone — research/<topic>/analysis.md is fine because it's explicitly an AI-synthesized doc — but daily notes, project journals, and people notes should be human-written. Agents read, humans write. That's the whole game.

Inbox bankruptcy. inbox/ becomes a graveyard the moment you stop processing it. If it has 40 files, you've already lost — declare bankruptcy, move everything to inbox/_archive-YYYY-MM/, start fresh next Monday.

Over-tagging. Tags feel like organization. They mostly aren't. Use folders for where something lives, wikilinks for what it relates to, and a small fixed tag vocabulary (about 10 max) for cross-cutting traits like #evergreen or #draft. Don't tag every concept — link them instead.

Deep folder hierarchies. Three levels is the practical ceiling. Going deeper means you'll lose track of where things live, which means you'll re-create them, which means link rot.

The vault's value isn't in any single feature. It's in the loop you run daily. Capture cheaply. Link liberally. Let synthesis happen on its own time. Crystallize manually. A reasonable test of whether this is working: a month from now, can you ask "what did I think about X back in May?" and get a useful, cited answer that surprises you? If yes, the system is doing its job. If not, you're either not capturing or not linking — both fixable in a week.

If the GUI ever feels limiting, there's an official Obsidian CLI — anything you can do in the app, you can do from the terminal: create notes, search, append, run scripts on a cron, drive the vault from automation

Open the vault. Type Cmd + P. Start.

Capture cheaply, link liberally, crystallize manually — the working loop that turns an Obsidian vault from a graveyard into a queryable archive of your own thinking.