Obsidian Project Memory

Maintain a filesystem-first, agent-driven Obsidian knowledge base for a research project.

Prefer this skill when working inside a repository that:

• already contains .claude/project-memory/registry.yaml, or
• clearly looks like a research project and should be bound to an Obsidian vault.

Core principles

• Use scripts for project state management.
• Use agents for project understanding and synthesis.
• Write only durable research knowledge into a small vault structure.
• Do not require MCP, API keys, REST plugins, or .base artifacts.
• Do not depend on .canvas globally, but allow literature workflows to maintain Maps/literature.canvas as a default literature graph artifact.
• Treat internal experiment summary reports as durable result-facing notes under Results/Reports/, not as Writing/ notes.

Default vault structure