This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
An Obsidian vault for personal-related notes. Synced across devices with Obsidian Sync. This is not a software project — there are no build, lint, or test commands.
Organized by the PARA method (Tiago Forte):
- 0_Inbox — unsorted captures, process regularly
- 1_Projects — active, goal-driven, time-limited work
- 2_Areas — ongoing subject matter areas (Career, Health, Real Estate, etc.)
- 3_Resources — reference material
- 4_Archive — inactive content kept for historical value
- .obsidian/ — Obsidian config (theme: Things, plugin: Copilot)
Agent-context files are marked with the agent-context frontmatter property, valued one of:
vault— global context: who I am, recurring people, long-running goals, life domains. Loaded every session, regardless of cwd.project— context for a single project under1_Projects/<X>/. Loaded when working inside that project folder.area— context for an ongoing area under2_Areas/<X>/. Loaded when working inside that area folder.
At the start of every session, load the relevant subset:
# Always: vault-scope (global personal context)
obsidian vault=ObsidianPersonal search query="[agent-context:vault]" format=json
# If cwd is inside 1_Projects/<X>/ — also load that project's context
obsidian vault=ObsidianPersonal search path="1_Projects/<X>" query="[agent-context:project]" format=json
# If cwd is inside 2_Areas/<X>/ — also load that area's context
obsidian vault=ObsidianPersonal search path="2_Areas/<X>" query="[agent-context:area]" format=json
# Then for each returned path:
obsidian vault=ObsidianPersonal read path="<returned path>"These files contain curated background, constraints, and goals — load and apply them before doing any work.
Authoring: when adding new agent-context files, set agent-context: <scope> and last-reviewed: <today> in frontmatter. Do not use the legacy #agent-context tag (migrated). See 2_Areas/Personal Knowledge Management/Obsidian PKM Methodology.md for the full convention.
For status values, tag style, and other vault-wide patterns, see 2_Areas/Personal Knowledge Management/Vault Conventions.md (loaded as vault-scope agent context).
- Markdown format: Obsidian-flavored markdown with
[[wikilinks]]for internal links - Linking: link related files using
[[File name]]wikilinks; look for files in the same folder or with shared tags - No secrets or credentials — this vault syncs across devices
Use the obsidian CLI for all vault reads/writes (respects indexing, templates, link resolution). Requires the desktop app to be running. vault=ObsidianPersonal must be the first parameter — placement matters. Prefer path= (vault-relative) over file= (wikilink resolution, can be ambiguous). See the /obsidian-cli skill for command reference.
- Do not modify
.obsidian/configuration files unless explicitly asked - The
.stignorefile controls Syncthing exclusions