Personal Knowledge Base Architecture
Use to create a simple knowledge system you can maintain each week.
Use case: Designs a personal knowledge base around retrieval and action, not collection. It works for study, professional development, or projects.
Best tools
- Notion — Combines notes, linked databases, templates, and searchable project context.
- Obsidian — Supports local markdown notes and lightweight linking between ideas.
Fill in your details
Answer the questions below. Your answers are placed into the prompt automatically.
Your filled prompt (preview)
You are my Personal Knowledge Base architect. Design a personal knowledge base architecture you will actually maintain.
========================================
PERSONAL CONTEXT (filled by me)
========================================
Purpose of the PKB: [PURPOSE]
Incoming sources: [SOURCES]
Tools you use: [TOOLS]
How you need to retrieve: [RETRIEVAL_NEEDS]
Tagging or linking preference: [TAGS_OR_LINKS]
Weekly time budget: [TIME_BUDGET]
Current pain points: [PAIN_POINTS]
Success looks like: [SUCCESS]
If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes.
========================================
WORKFLOW YOU MUST FOLLOW
========================================
STEP 1 — Jobs
Clarify knowledge jobs from [PURPOSE], [RETRIEVAL_NEEDS], and [PAIN_POINTS].
STEP 2 — Architecture
Design folders/databases/links for [TOOLS] and [SOURCES] using [TAGS_OR_LINKS].
STEP 3 — Cadence
Fit capture/review to [TIME_BUDGET].
STEP 4 — Bootstrap
Give a 7-day setup plan aimed at [SUCCESS].
========================================
OUTPUT FORMAT
========================================
Use these exact headings:
A. Knowledge jobs
B. Architecture map
C. Capture workflow
D. Retrieval patterns
E. Tag/link rules
F. Weekly cadence
G. 7-day setup plan
H. What not to build yet
Rules: maintainable > perfect ontology; reduce friction.
You are my Personal Knowledge Base architect. Design a personal knowledge base architecture you will actually maintain. ======================================== PERSONAL CONTEXT (filled by me) ======================================== Purpose of the PKB: [PURPOSE] Incoming sources: [SOURCES] Tools you use: [TOOLS] How you need to retrieve: [RETRIEVAL_NEEDS] Tagging or linking preference: [TAGS_OR_LINKS] Weekly time budget: [TIME_BUDGET] Current pain points: [PAIN_POINTS] Success looks like: [SUCCESS] If any field is blank or still shows brackets, list the gap, continue with labelled assumptions, and never invent unverified facts, numbers, citations, or quotes. ======================================== WORKFLOW YOU MUST FOLLOW ======================================== STEP 1 — Jobs Clarify knowledge jobs from [PURPOSE], [RETRIEVAL_NEEDS], and [PAIN_POINTS]. STEP 2 — Architecture Design folders/databases/links for [TOOLS] and [SOURCES] using [TAGS_OR_LINKS]. STEP 3 — Cadence Fit capture/review to [TIME_BUDGET]. STEP 4 — Bootstrap Give a 7-day setup plan aimed at [SUCCESS]. ======================================== OUTPUT FORMAT ======================================== Use these exact headings: A. Knowledge jobs B. Architecture map C. Capture workflow D. Retrieval patterns E. Tag/link rules F. Weekly cadence G. 7-day setup plan H. What not to build yet Rules: maintainable > perfect ontology; reduce friction.
Pro tip: Design around how you will retrieve notes, then limit capture fields.
Expected output: A maintainable knowledge-base structure with templates and routines.