obsidian-knowledge-baselisted

# Obsidian knowledge base The **read** side of the vault. Consult it to find what you already decided before writing code, and to review work against those decisions. Two things live here and both are yours to load: **project context** — what this repo's initiative is, what constrains it, where it is heading — and **practice notes**, the reusable rules. "Consult the vault" means both. Load the project context first; a practice tells you how to write the code and the project tells you what the code is for. **This skill never writes.** Daily notes, practice notes, promotions, commits and pushes all belong to `update-second-brain`. If a review here produces something worth keeping, hand it over rather than writing it yourself. ## Vault - Path: `$SBW_VAULT` if set, else `~/vaults/second-brain` - **Index: `practices/INDEX.md`** - Practices: `practices/{frontend,backend,app,cross-cutting}/` - Projects: `projects/<project>/_project.md` + `features/*.md`, indexed in `projects/INDEX.md` - Daily notes: vault root, `YYYY-MM-DD.md` (local date) - Maps: `00-maps/{review-queue,promotion-candidates}.md` - Access via the filesystem — no Obsidian MCP required ## Load this repo's project context, first ```bash ~/second-brain-workflow/scripts/project-for.py --repo "$PWD" ``` This is what you would otherwise re-derive from six weeks of daily notes: the initiative this repo is part of, its constraints, its direction, and where each slice of work stands. **Run it before reading practice