init-vault

Scaffolding a structured Obsidian vault creates a ready-to-use skeleton with canonical folders and core files like WORKSTATE.md, ARCHITECTURE.md, and README.md. The skill guides you through vault naming, layout selection, and location to prepare the structure for immediate use.

An Obsidian vault supporting living-docs auto-update requires core files including WORKSTATE.md, CHANGELOG.md, CLAUDE.md, seed notes, and per-folder READMEs. These files are automatically created and wired to the pipeline during the vault scaffold process.

Yes, you can initialize Git for a new Obsidian vault alongside a paired code repository. During the scaffolding process, the skill prompts you for a paired repo location and offers optional Git initialization to link your notes vault directly with your codebase.

Setting up a topical knowledge vault uses a canonical layout with standard folders like reference/ and notes/. The scaffolding process prompts you to select a topical vault type, automatically generating the appropriate folder structure and seed content for immediate knowledge organization.

Organizing an Obsidian vault for Claude Code sessions requires a canonical layout with CLAUDE.md and ARCHITECTURE.md at the top level. This scaffolding skill creates these required files and indexes, ensuring the vault structure is prepared for direct integration with Claude Code workflows.

Scaffolding an Obsidian vault requires no existing dependencies or plugins. The skill operates independently to generate the canonical folder structure and required markdown files at your specified path, preparing the vault for native Obsidian use and living-docs auto-update hooks.