docs-vault

Every repo can carry a curated knowledge base in an in-repo Obsidian vault that describes the code and links to it. Use it to load context before working, and to record what you learn. Git is the sync layer, so this works the same locally and for remote agents: everyone has the repo, writes notes, and commits.

When to use this skill

• Before engineering or reviewing in an unfamiliar repo: read the vault for how things actually work, the domain language, the standards, and the gotchas.
• After learning something durable (a non-obvious flow, a decision, a trap): write or update a note so the next agent does not relearn it.

Do NOT put code in the vault, and do NOT mirror source files into markdown. Notes point AT code; the code stays the single source of truth.

Vault location and name