Personal Knowledge Base — Build a Searchable Second Brain
Build a searchable second brain that captures insights with topic clusters and connections between ideas. Never lose a brilliant idea again — Claude Code finds and synthesizes your notes on demand.
You read 50 articles a month and remember almost nothing. Highlights sit in Pocket, notes scatter across apps, and when you need that perfect analogy from a book you read last year — it's gone. A second brain only works if you can actually search and connect what's in it.
Who it's for: lifelong learners who consume more than they retain, researchers building personal reference libraries, writers collecting ideas and references for future projects, educators organizing subject matter knowledge for teaching, knowledge workers who want to compound what they learn over years
Example
"Build me a searchable knowledge base from my reading notes" → Organized second brain with topic clusters, bi-directional connections between ideas, search across all entries, auto-generated insight summaries, and weekly 'rediscovery' prompts surfacing relevant past notes
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Personal Knowledge Base
## Role
You help me build and maintain a searchable personal knowledge base. You capture insights using a consistent template, maintain a topic index, and synthesize knowledge when I need it.
## Directory Structure
- `knowledge-index.md` — Master index organized by topic clusters
- `notes/` — Individual insight notes using the standard template
- `syntheses/` — Synthesized summaries across multiple notes
## Note Template
For each note in `notes/[topic]-[short-title].md`:
- **Source**: Where this came from (book, article, conversation, experience)
- **Date**: When captured
- **Core Insight**: The key idea in 1-2 sentences
- **Why It Matters To Me**: Personal relevance and application
- **Connections**: Links to other notes in the knowledge base
- **Questions Raised**: What I still want to explore
- **Tags**: Topic tags for the index
## Rules
1. Every note must use the template — consistency enables search
2. Always check the index for connections when adding a new note
3. Update the index whenever a new note is added
4. Syntheses should reveal new insights, not just summarize
5. Questions raised are as valuable as answers captured
## Commands
- "/capture [insight]" — Create a new note using the template
- "/index" — Show or update the knowledge index
- "/connect [note]" — Find connections between a note and existing knowledge
- "/synthesize [topic]" — Synthesize all notes on a topic
- "/search [query]" — Search the knowledge base for relevant notes
- "/gaps [topic]" — Identify gaps in knowledge on a topicGet new playbooks like this one
One email a week with new Claude Code workflows. Free, like everything here.
No spam. Unsubscribe anytime.
What This Does
Solves the "I read something brilliant and can't find it" problem. Captures insights in a structured, searchable format with topic clusters and connections between ideas. Claude can query your knowledge base to find relevant notes and synthesize what you've learned.
Inspired by Marco Kotrotsos's 20 Non-Coding Uses for Claude's Code Mode.
Prerequisites
- Claude Code installed
- Ideas, articles, or insights you want to capture
- A few topic areas you're interested in
Step-by-Step Setup
- Create your knowledge base folder with
notes/andsyntheses/subfolders - Save the CLAUDE.md template
- Define your initial topic clusters in the index
- Start capturing insights one at a time
- Periodically synthesize and search
Example Usage
"I want to capture this insight about habit formation from Atomic Habits"
"Add it to the knowledge base — suggest which cluster and connections"
"I'm thinking about motivation — search my notes for relevant insights"
"Synthesize everything I've captured about leadership"
"What gaps do I have in my understanding of decision-making?"
Tips
- Capture immediately when you encounter an insight — delayed capture loses context
- The "Why It Matters To Me" field is what makes notes useful later
- Connections between notes are where new ideas emerge
- Run synthesis periodically — patterns aren't visible one note at a time