This repo contains the folder structure + workflows I use to run my “second brain” in Obsidian.
It’s built around Zettelkasten / atomic notes: small, self-contained ideas that link together to form a knowledge graph. Don't worry about structure, the folders are just here to be used as a guideline, not a rigid filing cabinet.
If you clone this repo into Obsidian, you’ll get:
- A clean, opinionated structure
- A system for projects, references, and tags that stays flexible as your life changes
If you do not have Obsidian you can download it here: https://obsidian.md/
Purpose: Capture raw, pictures, documents, links, and messy thoughts quickly.
-
Use this as your inbox.
-
Meeting notes, brain dumps, random ideas, clipped text, half-formed thoughts.
-
Don’t worry about structure here. The only rule: capture first, and use tags/ references to make connections.
Typical examples:
-
2025-11-13 – Morning brain dump.md -
Random idea – marketing flywheel for local businesses.md -
Meeting – Client X discovery call.md
Later, you’ll process these into Atomic Notes, Direct Tags, or Indexes.
Purpose: Store external inputs and references.
This is your reference library for:
-
PDFs, ebooks, articles
-
Lecture notes, slides, screenshots, web clippings
-
Photos of whiteboards
-
Contacts / “rolodex” style notes
-
Issues / tickets / problem statements (that you can reference later)
You can either:
-
Store files directly inside here (
/PDFs,/Screenshots, etc.), or -
Create “Source notes” that summarize a book, video, or article and link to the file.
Example:
-
Books/How to Take Smart Notes.md -
Videos/YouTube – Zettelkasten workflow walkthrough.md -
Contacts/Jane Doe – Product Manager @ Company.md
Purpose: High-level concept buckets that will be referenced often.
Think of Direct Tags as evergreen topic hubs (but file-based, not hashtags).
These are notes you’ll jump to frequently, like:
-
Productivity.md -
Cybersecurity.md -
Obsidian.md -
Marketing.md -
Projects.md
Inside each Direct Tag note:
-
Add a brief explanation of the topic
-
Manually curate important links to Atomic Notes, sources, and indexes
-
Optionally add a section like:
## Related Notes - [[202511131230 – Deep work vs shallow work]] - [[202510221015 – Task batching workflow]] - [[Index – Focus Systems]]
Direct Tags = big buckets you revisit every week.
Purpose: High-resolution maps of specific areas using
[[links]].
Where Direct Tags are broad buckets, Indexes are more curated and structured.
Good candidates for Indexes:
-
A specific project area
Index – EcommBeam SaaS.md
-
A life domain
Index – Career Development.md
-
A research theme
Index – Embedded Cybersecurity.md
Inside an Index:
- Break things down by section:
# Index – Embedded Cybersecurity ## Core Concepts - [[202510011200 – Threat modeling for avionics]] - [[202510041530 – RF attack surfaces overview]] ## Projects - [[Project]] - [[Project Program]] ## References - [[NIST 800-53 Summary]] - [[Notes]]
Indexes = “table of contents” notes for key domains.
Purpose: Speed up consistent note creation.
Use this folder to store Obsidian templates you can quickly apply via the Templates:
Common templates:
-
Template – Daily Note.md -
Template – New Contact.md -
Template – Issue / Problem.md
Adapt these to your style—but keep templates simple and repeatable.
Purpose: The core of the system – small, self-contained notes that each express one idea.
This is where your processed, long-term knowledge lives.
Rules of thumb for Atomic Notes:
-
One idea per note
-
Named clearly, e.g.:
-
202511131230 – Why atomic notes reduce friction.md -
202510251045 – Benefits of local-first software.md
-
-
Each note stands alone: someone else should be able to read it and understand the core idea.
-
Use links, not folders, for structure:
-
Link to Direct Tags (
[[Productivity]]) -
Link to Indexes (
[[Index – Cybersecurity]]) -
Link to related atomic notes via
[[...]]
-
Over time this becomes your network of thoughts.
Here’s a simple daily workflow to get value from this structure:
-
Dump thoughts into
1. Rough Notes. -
Don’t edit yourself—just capture.
On a regular basis (daily or weekly):
-
Open
1. Rough Notes. -
For each rough note:
-
Extract any idea worth keeping into a new Atomic Note in
6. Atomic Notes. -
Link that Atomic Note to:
-
At least one Direct Tag (e.g.
[[Productivity]]) -
Any relevant Indexes
-
-
-
Delete or archive the processed Rough Note.
As you add more atomic notes:
-
Link related ideas together using
[[ ]]. -
Update your Direct Tags and Indexes:
-
Add new important links.
-
Reorganize sections as topics mature.
-
This keeps the system alive and discoverable, instead of a static filing cabinet.
-
Clone or download this repo.
-
In Obsidian:
-
Open the
Master Brainfolder as a Vault, or -
Move the structure into an existing vault.
-
-
Enable helpful core plugins (recommended):
-
Daily notes
-
Templates
-
Backlinks / Graph view
-
-
Create your own templates under
5. Templates. -
Start capturing in
1. Rough Notesand gradually building6. Atomic Notes.
You can use any naming system, but here’s a simple pattern:
-
Atomic Notes:
YYYYMMDDHHmm – Short, descriptive title.md
e.g.202511131045 – Benefits of atomic notes.md -
Indexes:
Index – Area or Topic.md
e.g.Index – Career Development.md -
Projects:
Project – Name.md
e.g.Project – Launch Obsidian template repo.md
Consistency helps future-you find things fast.
Q: Do I have to use all these folders?
No. This is a starting point. If something feels redundant or you don’t use it, delete or merge it.
Q: Where do tasks / to-dos go?
You can:
-
Put quick tasks inside Rough Notes or Daily Notes, or
-
Maintain a dedicated project note in
6. Atomic Notesand manage tasks there.
Q: How “pure” Zettelkasten is this?
This setup is inspired by Zettelkasten and atomic notes, not a strict academic implementation. It’s meant to be practical and flexible.
If you fork / adapt this template, feel free to:
- Add your own examples
- Share screenshots of your layout
- Open issues with ideas or improvements
Released under the MIT License Feel free to use, adapt, and share.