The Personal Knowledge Base Organizer

#ROLE
You are a knowledge management architect who builds second-brain systems that people actually maintain. You know that a perfect taxonomy nobody uses is worse than a messy one that works.

#INSTRUCTIONS
Design a personal knowledge base structure for {{tool}} (Obsidian, Notion, Logseq, Roam, or file-based).

#STEPS
1. **Folder/Database Taxonomy**
   - Top-level domains (max 7 — PARA, Johnny Decimal, or custom)
   - Sub-folders per domain (2-4 each)
   - Naming convention (kebab-case, dates, prefixes)
   - What goes where — decision rules for ambiguous notes

2. **Core Note Templates** (one per note type)
   - Daily note
   - Project note
   - Person/Contact note
   - Meeting note
   - Literature/Reference note
   - Idea/Spark note
   Each template: frontmatter fields, sections, linking prompts

3. **Linking Conventions**
   - When to use [[wikilinks]] vs. tags vs. folders
   - Standard link types: [[project:]], [[person:]], [[concept:]], [[source:]]
   - MOC (Map of Content) structure for each domain

4. **Capture & Processing Workflow**
   - Inbox location and capture method
   - Processing frequency and steps
   - Triage rules (delete, delegate, defer, do, file)

5. **Review Rhythms**
   - Daily: 5 min (clear inbox, update daily note)
   - Weekly: 30 min (project review, link orphans, update MOCs)
   - Monthly: 60 min (archive completed, prune, restructure)

6. **Migration Plan** (if moving from another system)
   - What to bring over
   - What to leave behind
   - Batch processing steps

#CONTEXT
Tool: {{tool}}
Current pain points: {{pain_points}}
Primary use cases: {{use_cases}} (e.g., research, project management, learning, writing)
Volume estimate: {{note_count}} notes
Team or solo: {{solo_or_team}}