How To Build The ULTIMATE AI Second Brain (Obsidian + Claude Code)

Summary of technological concepts & system setup

The video demonstrates building an “AI second brain” using Obsidian as the knowledge/projects workspace and Claude (an LLM) as an agentic assistant—specifically leveraging Claude Code and an Obsidian integration plugin.

Core idea: a 2-layer agent system

1. Layer 1 (Strategy + Context / “General”)

   • Claude acts as a thinking partner to answer: “What do we do?”
   • It works by giving Claude shared, personalized context from:
     • goals, journals, calendar
     • notes/books/videos/courses
     • long-term strategy journal
     • project list
     • reviews (weekly/monthly/quarterly/yearly templates mentioned)
   • Main mechanism: a Claude.md instructions file inside the Obsidian folder (e.g., the “brain” vault) that tells Claude:
     • who you are, your goals/rules
     • Claude’s role (thinking partner, not “doing everything”)
     • available skills/commands

2. Layer 2 (Project Execution / “AI soldiers”)

   • Each project folder answers: “How do we do it? Then we do it.”
   • You open a project as its own Obsidian vault (using Obsidian “manage vaults → open folder as a vault”), so Claude is focused on the project’s scope.
   • Claude becomes a “digital employee” with project-specific:
     • inputs (ideas, requirements)
     • process instructions (research, drafting, design, etc.)
     • outputs (the deliverable)
   • Examples of project structure:
     • YouTube project: inputs (video ideas), process (research/title/thumbnail/content), feedback (metrics/comments)
     • Finances project: drop statements → build budget → categorize → monthly report → analysis

---

Key tools, plugins, and features emphasized

1) Obsidian as the “folder viewer on steroids”

• Treats Obsidian as a customizable file/folder workspace for knowledge work.
• Used for:
  • persistent structure (vaults/projects)
  • storing notes/skills/templates
  • hosting Claude inside the workflow

2) Claude Code installation via terminal

• Claude Code is installed so Claude can be used more “inside” the local workflow.
• Includes verifying trust/permissions in terminal and confirming installation.

3) “Claudian” Obsidian plugin (Claude inside Obsidian)

• The video uses an Obsidian community plugin (referred to as Claudian) to:
  • embed Claude chats into the Obsidian UI
  • attach Claude to the currently opened project context
• Install method includes:
  • copying a GitHub repo link into Claude to review/install
  • selecting which vault to install into (the user’s “brain vault”)
• Troubleshooting advice:
  • screenshot any error and ask Claude to help
  • often requires restarting Obsidian

4) Claude “skills” system (automation recipes)

• The system uses skills (instructions/commands Claude can run).
• Skills are stored either:
  • in downloaded Claude skill folders, or
  • as Markdown skill files inside the project’s 05 skills folder (personal preference)
• A setup flow runs a skill like “new project” and weekly update (interviewing the user to refresh context).
• Project creation is automated: “new project skill” generates the project folder structure + Claude.md for that project.

5) “Dispatch” for remote phone → computer capture

• Bonus workflow: using Claude desktop app “Dispatch” to access the second brain remotely.
• Claims:
  • can keep the computer awake and bypass permissions (also mentions “safe mode”)
  • from a phone, save ideas into the correct Obsidian folder
• Warning:
  • Dispatch can be glitchy, especially initial setup, but is powerful once stable.

6) Team syncing via Obsidian Sync

• Bonus tip: Obsidian Sync to share vaults with collaborators.
• Mentions:
  • “Sync” plugin enabled
  • choose remote vault and invite team by email
  • option to sync all file types, and exclude folders as needed

---

Step-by-step tutorial highlights (setup flow)

• Download:
  1. Claude desktop app (Claude.com)
  2. Obsidian
  3. A provided KJOS template vault folder (from a free classroom/resources area)
• Rename the template vault to the user’s preferred name.
• Install Claude Code via terminal.
• Open Obsidian vault and trust plugins.
• Install Claudian plugin and configure Claude within Obsidian.
• Run an Obsidian skill in the 05 skills folder (setup), where Claude asks rounds of questions to generate Claude.md:
  • communication boundaries
  • strengths/weaknesses
  • goals and current progress
  • current projects
• Then run “new project skill” to generate a first project (example: “finances”).
• Open a project as a separate vault to enter Layer 2, where Claude is scoped to that project only.

---

Use cases demonstrated (practical applications)

A) Building an app (“Signal” app / YouTube 2.0)

• Uses project structure to manage:
  • inputs (ideas/features)
  • development board (with plugin)
  • Claude to design features/specs and test UI in HTML
  • co-founder/developer synced via Obsidian Sync
• Mentions Claude MD to role-separate:
  • Claude helps design/testing, while developer Claude instances implement/spec into the live site.

B) Email marketing client automation

• Skill-based pipeline:
  • generate email ideas from client context + content/news
  • draft rough sales emails with specified CTA and goal
  • review by Claude + sub-agent(s)
  • user finalizes (“finishing touches”) and ships

C) Main YouTube channel production system

• Video ideation pipeline:
  • validate demand with VidIQ + AI
  • use Signal to find and summarize top competitor videos
  • skill for “packaging research”:
    • direct competitors
    • similar videos (thumbnail ideas)
    • keyword analysis (sweet spots, competition vs traffic)
    • title structure suggestions
    • thumbnail element comparisons
    • ranked/optimized title ideas + thumbnail checklist
    • auto-generated tags
• Content creation:
  • Claude helps outline, intro structure, and guidance (user ships final content)
• Collaboration:
  • editor uses synced Obsidian and Claude for editing/suggestions
• Iteration:
  • metrics + personal lessons recorded back into the Obsidian project

D) Daily YouTube channel system

• Dispatch captures ideas from the phone into structured “ideas” folders.
• Skills generate:
  • multiple title options (based on creator’s style)
  • structured note capture (origin/date/etc.)
  • thumbnail selection: AI extracts screenshot candidates; user edits in Photoshop; Claude handles upload/title/description/scheduling
• Emphasizes iteration on skills like speaking/recording/lighting.

E) Coaching/consulting client workflow

• Uses client folders with templates:
  • call agenda + post-call notes
  • transcripts/transcript-derived timestamps (generated via Claude skill)
• Outputs are copied into a course/school area for the client.

---

Review/quality analysis and “bonus tips” (framework guidance)

1. Market cares about outputs, not processes

   • Automate carefully: if output quality drops (“slop”), don’t automate that part yet.
   • Use AI to do research/automation while humans apply judgment where it matters (e.g., thumbnails manually).

2. Personalization is mandatory

   • Don’t copy blindly—structure must match your life/business.

3. AI is a skill you must practice

   • Learn by doing and collaborating with the system, not endlessly watching videos.

4. Have fun / start small

   • Build enjoyable projects first rather than trying to “conquer everything” instantly.

---

Main speakers / sources

• Speaker/creator: “KJ” (the narrator and system builder; references like “check out my free school,” “my editor Caleb,” and “Signal app” are used throughout).
• AI systems/tools referenced: Claude (Claude Code, Claude desktop app / Co-work / Dispatch) and Obsidian (plus Claudian plugin, Obsidian Sync, and video/market tools like VidIQ + AI).