What problem does it solve? Setting up a new Obsidian vault for use with Claude Code requires consistent folder structure, governance rules, and frontmatter conventions — doing this manually is error-prone and produces vaults that downstream knowledge skills cannot reliably process. ## Core Features & Use Cases - Guided Vault Bootstrap: Runs a short interview (purpose, topics, note types, frontmatter style, tag taxonomy) or accepts --minimal defaults, then scaffolds a PARA+Zettelkasten folder layout. - Governance File Generation: Writes a customized CLAUDE.md covering Obsidian syntax rules, note naming conventions, wikilink handling, and vault-specific don'ts, plus a .mz/vault-schema.yml defining per-note-type frontmatter requirements. - Non-Destructive Retrofit: Detects existing CLAUDE.md, schema, and folders, merging missing sections instead of overwriting, with an explicit approval gate before any files are written. - Use Case: Point the skill at a new or existing vault directory, approve the scaffold plan, and receive a vault ready for downstream skills like vault-ingest, process-notes, and vault-schema. ## Quick Start Ask the assistant to initialize a new Obsidian vault at a given path, for example by saying: bootstrap my Obsidian vault at ~/Notes with the default structure.
