FREE PROJECT Second Brain 2.0

Slide 1

FREE PROJECT Second Brain 2.0

FREE PROJECT Second Brain 2.0 (with Claude) Graph view x + ← → Graph view <% > + ✉️ Inbox > > + 🗺️ Maps > > + 🧠 Body of Work > > > ✍️ Notes > > > 💡 Ideas > > > 🌲 CHS Work > > > 🚀 Projects > > > 🗺️ Areas > > > 📚 Library > > > 📖 Journal > + Home > ⚡ Recent Notes

Slide 2

This is part 2 of our AI Second Brain Series! You can do this project with no experience.

Slide 3

#1 Get your vault ready Install Claude Code Desktop and open your second-brain vault with CLAUDE.md and four slash commands ready. Obsidian Version 1.12.7 Quick start Create new vault Create a new Obsidian vault under a folder. Create Open folder as vault Choose an existing folder of Markdown files. Open Open vault from Obsidian Sync Set up a synced vault with existing remote vault. Sign in English (GB)

Slide 4

#2 Back up and connect your tools Push your vault to a private GitHub repo, set up Obsidian Git auto-sync, and wire in your first MCP Connector. Create a new repository Repositories contain a project's files and version history. Have a project elsewhere? Import a repository. Required fields are marked with an asterisk (*). 1 General Owner * minimus7 / second-brain second-brain is available. Great repository names are short and memorable. How about cuddly-parakeet? Description My AI second brain vault, synced with Claude Code 49 / 350 characters 2 Configuration Choose visibility * Choose who can see and commit to this repository Private Add README READMEs can be used as longer descriptions. About READMEs Off Add .gitignore .gitignore tells git which files not to track. About ignoring files No .gitignore Add license Licenses explain how others can use your code. About licenses No license

Slide 5

You'll learn how to customise your second brain to your own use cases!

Slide 6

#3 Auto-ingest your sources Build a /pull-sources slash command that pulls fresh material from your tools straight into raw/ for /ingest gro-75-set-up-rotating-daily-growt Properties source linear captured 21 / 04 / 2026 issue_id GRO-75 title Set up rotating daily growth metric reporti status Done team Growth priority Medium url https://linear.app/nextwork/issue/GRO-75/ Add property

Slide 7

#4 Create your priorities document Write priorities.md with Projects, Areas, Resources, Archive, and Key People so Claude knows what matters. second-brain/ ├── raw/ # Source documen │ ├── claude-exports/ # Exported Claud │ ├── granola-notes/ # Meeting notes │ └── notion-exports/ # Pages/database ├── wiki/ # Claude's domai │ ├── index.md # Master catalog │ ├── log.md # Append-only ac │ ├── concepts/ # Concept and to │ ├── projects/ # Project-specif │ └── people/ # People dossier ├── journal/ # Daily notes (P ├── content/ # Content pipeli └── priorities.md # User-maintaine /briefing and /debrief)

Slide 8

#5 Build and run your daily loop Ship /briefing and /debrief slash commands, then run a full morning-to-evening loop end-to-end Build and Test /debrief /briefing is a one-shot read that hands you context. /debrief is different. It's a conversation. It asks you a few short questions, writes a structured entry to your wiki, and can propose updates to other pages before making changes. Because the prompt is bigger, you'll have Claude Code Desktop write the command file for you. * In Claude Code Desktop, confirm your vault project is selected. * Paste this prompt into the chat and press Enter: markdown Create .claude/commands/debrief.md that: 1) Reads priorities.md for today's focus. 2) Asks me 3-4 short questions one at a time: What did you accomplish 3) Writes a structured entry to wiki/log.md with a timestamp and "typ 4) If answers mention existing wiki pages, update them. If something 5) If priorities shifted, suggest updates to priorities.md but ask fi 6) End with a one-line summary of the day. $ARGUMENTS is optional. If provided, skip the questions and use $ARGU

Slide 9

#6 Schedule your briefing as a cloud routine Turn /briefing into a remote Cloud Routine that runs on a schedule and commits to your vault automatically. Introducing routines in Claude Code Define repeatable routines that work your backlog, your PRs, and respond to events in the cloud.

Slide 10

Get the entire project guide & more advanced tips 👇 learn.nextwork.org