Vault init

Copies the starter vault to the user's vault path. The starter holds the folder conventions, a CLAUDE.md template with {{PLACEHOLDERS}}, a commented .vsearchignore, an inbox README, and one example atom and MOC.

Steps

1. Pick the path. Use the argument if the user gave one. Otherwise use $VAULT_PATH if set, else ~/vault. State the path in one line before copying.

2. Check the target. If the path exists and holds files, list what is there and ask before going on. Never delete or replace anything in it.

3. Copy without overwriting.

   mkdir -p "<path>"
   rsync -a --ignore-existing "${CLAUDE_PLUGIN_ROOT}/templates/vault-starter/" "<path>/"
   

   Without rsync, use cp -Rn "${CLAUDE_PLUGIN_ROOT}/templates/vault-starter/." "<path>/". Hidden files (.vsearchignore, .gitignore) must come across.

4. Report. List the files copied and any that already existed and were skipped.

5. Point at the search path. The plugin's vault-search MCP server reads the vault path from the plugin option vault_path (default ~/vault). If the user picked another path, tell them to set it: claude plugin configure vault@<marketplace> or reinstall with --config vault_path=<path>, then restart Claude Code.

6. Next step. Tell them to run /vault:seed. It replaces the starter's generic structure with one built from their own domains.