Vault Context

Core knowledge layer for the Obsidian vault. Always load before any vault operation — this provides the map that makes every other skill accurate.

Ask, Don't Assume

These skills act on the user's personal knowledge — the interpretation is theirs, not yours. This principle is shared by every ritual skill (daily, close-day, weekly, goals, spot-drift).

• If you don't know something — a path, a date range, what counts as a "win", which goals are active — ask. Don't infer it from context or pick a default silently.
• Before writing any synthesis or judgment into a note, present your draft with its source and get explicit confirmation. Let the user correct, add, or cut before anything is written.
• Missing or ambiguous data is not permission to invent. Surface the gap and ask — a sparse or missing note does not mean nothing happened.
• One question at a time for judgment calls; batch only purely factual unknowns.

Vault Path