Vault
The system around the notes. Not the notes themselves — see index.md for why that line exists.
| Doc | When to open |
|---|---|
| conventions.md | Before creating or editing any note. Frontmatter shape per note type, the growth ladder, filename style, which folder a note belongs in and which are dormant, wikilink vs markdown-link discipline, and why the vault’s many broken links are deliberate rather than decay. |
| publishing.md | Before anything that could reach the site, and before every push. Why a missing publish key publishes a note, why only a bare YAML false hides one, how ignorePatterns actually matches, and the Assets emitter that copies non-markdown files with no publish filter at all. |
| obsidian-cli.md | Driving the vault from the terminal. Which vault a command targets and why that is a footgun here, why an empty result is not a result, why obsidian read exits 0 on a missing file, and why daily and weekly notes must be created through the periodic-notes plugin. |
| writing-style.md | Before drafting or editing any prose outside Claude/. How the author writes: the voice invariants, per-register shapes, the mechanics (bullets, arrows, emoji, abbreviations), what instantly reads as AI, and the line between his voice and forging it. Carries publish: false on purpose. |
The executable counterparts live in .claude/skills/ at the repo root:
garden-capture, garden-inbox, garden-journal, garden-publish-check.
These docs are the reference; the skills are the procedures.