CLAUDE
Knowledge Discovery Vault — Operating Manual
This is an Obsidian knowledge vault at /home/firas/resources/vaults/knowledge-discovery.
Claude Code operates here as a personal knowledge assistant, research partner, and task manager.
Vault Overview
| Folder | Purpose |
|---|---|
Daily Notes/ | One note per day — tasks, reflections, logs |
Topics/ | Evergreen concept notes (atomic ideas) |
MOCs/ | Maps of Content — index notes linking related topics |
Projects/ | Active project notes and sub-folders |
Goals/ | 3-year vision, annual, quarterly goals |
Research/ | Deep research outputs (GSD-driven multi-phase) |
Resources/ | Books, articles, references |
Templates/ | Note templates — never edit directly, copy to use |
Inbox/ | Quick captures — process weekly |
Archives/ | Completed projects, old notes |
Skills Available
| Skill | Trigger | Path |
|---|---|---|
obsidian-research | /research, research tasks | .claude/skills/obsidian-research/SKILL.md |
daily-pkm | /daily, morning/evening routines | .claude/skills/daily-pkm/SKILL.md |
task-mgmt | /task, project management | .claude/skills/task-mgmt/SKILL.md |
Always check .claude/skills/ for the locally-installed versions of skills first.
Global skills are at ~/.claude/skills/.
GSD Research Rules
When research requires multi-phase investigation (> 30 min of work or multiple domains):
- Use
/gsd:new-projectto scaffold the research project - Research outputs go in
Research/<topic>/ - Each research session gets a folder:
Research/<topic>/YYYY-MM-DD/ - Final synthesis goes in
Topics/<concept>.mdwithsource::links back to research - The
vault-researcheragent (.claude/agents/vault-researcher.md) handles vault-integrated research
Non-Negotiable Vault Conventions
Note Naming
- Daily notes:
YYYY-MM-DD.mdinDaily Notes/ - Topic notes:
Title Case With Hyphens.mdinTopics/ - No spaces in filenames — use hyphens
Frontmatter (required on all non-daily notes)
---
title: Note Title
date: YYYY-MM-DD
tags: [tag1, tag2]
type: topic|project|research|resource|moc
status: active|draft|archived
---Linking
- Always use
[[wikilinks]]for internal links - Use
[[Note Title|display text]]when display text differs - Add backlinks section at bottom of topic notes
Tags
- Use lowercase hyphenated tags:
#machine-learning,#book-notes - Category tags:
#area/work,#area/personal,#area/learning
Inbox Processing
- Captures go to
Inbox/YYYY-MM-DD-capture-title.md - Process inbox weekly during
/weeklyreview - Either promote to Topics, link to Projects, or delete
Session Start Protocol
On session start, Claude should:
- Read
VAULT-INDEX.mdfor current context - Check
git log --oneline -5for recent changes - Check
Inbox/file count - Report active projects and today's note status
Commit Convention
Auto-commits (via hooks) use: vault: <action> <filename>
Manual commits: vault: <description of knowledge work done>
Subagent Instructions
All subagents (GSD executors, researchers, planners) spawned in this vault must:
- Read this CLAUDE.md before any action
- Follow note naming and frontmatter conventions above
- Write research outputs to
Research/not to root - Link new notes into relevant MOCs when creating topic notes
- Never delete notes — move to
Archives/instead - Commit after completing each discrete knowledge task