Obsidian vault

Routes natural language capture requests to the appropriate slash command.

Routing table

How to route

1. Parse user's natural language to identify intent
2. Extract relevant values (amount, category, duration, description, etc.)
3. Follow the corresponding command's instructions to execute
4. For work notes, prefix the content with the project name and a colon (example: atlas-metrics: ...). Do not add a literal project: prefix. Infer the project from context when possible. If unknown, ask for the project name.

Command locations

All commands are in ~/.claude/commands/:

• task.md - add tasks
• spend.md - log spending
• workout.md - log workouts
• evening.md - log build/drift evenings
• note.md - capture notes
• list.md - add to lists
• save.md - log savings deposits
• weekly.md - weekly review
• month-review.md - monthly review
• bored.md - combat drift with suggestions
• done.md - mark list items complete
• sync.md - sync vault or configs to GitHub
• deepplan.md - deep planning with research
• pull-context.md - pull vault context for a topic

Scripts (for command internals)

Commands use these scripts. Do not construct entry formats manually.

• {baseDir}/scripts/add-entry.sh <section> <params...> - validates, constructs, and inserts entries
• {baseDir}/scripts/inbox-path.sh - get current inbox path
• {baseDir}/scripts/get-month-data.sh YYYY-MM - extract month data
• {baseDir}/scripts/sync-repo.sh <path> [status|commit|pull|push] - git sync with safety
• {baseDir}/scripts/lint-inbox.sh [YYYY-MM] - audit inbox for format issues

add-entry.sh parameter reference

Data formats

See {baseDir}/references/data-formats.md for entry specifications.