Write a detailed explanation of the work just completed and save it to the Obsidian vault.
Target Detection
- •If $ARGUMENTS contains a project slug or "general", use that
- •Otherwise, classify based on what the session work was about, not just the working directory:
- •If the work modified vault templates, skills,
~/.claude/config, or general tooling -> usegeneral - •If the work was on project-specific code, features, or bugs -> detect from working directory using the project slug mapping in CLAUDE.md
- •If the work modified vault templates, skills,
- •If no mapping matches, default to
general
Steps
- •Read the relevant template at
~/AIVault/_templates/explanation.md - •Determine a kebab-case slug for the filename based on the work done
- •Write to
~/AIVault/projects/{project-slug}/explanations/{slug}.md(or~/AIVault/general/explanations/{slug}.mdfor general work) - •Fill in YAML frontmatter: date, tags, status (complete), project, type (explanation)
- •Use full-path wiki-links with display names:
[[path/to/file|Display Name]] - •Add a
## Relatedsection at the end with cross-links to related vault documents - •Update the relevant
{scope}-home.mdMOC with a link to the new document- •Project:
~/AIVault/projects/{project-slug}/sfdb-home.md(or equivalent) - •General:
~/AIVault/general/general-home.md - •Root:
~/AIVault/vault-home.md
- •Project:
Formatting
Reference the obsidian-markdown skill for Obsidian-flavored markdown conventions (callouts, embeds, etc.).
Content
Walk through what was built, how it works, key design decisions, and lessons learned. Act like a senior engineer teaching the code.