init-vaultlisted
Install: claude install-skill YoniRaviv/dev-llm-wiki
# Init Vault
Personalizes a freshly-cloned claude-dev-wiki template. When it finishes: the tracker is named, the
date format matches the user's preference, `raw/` holds only the capture surfaces they'll use,
`wiki/topics.md` carries a starter vocabulary for their stack, the harness has a scoped permission
allowlist, and **the pre-commit gate is installed** — so the vault's invariant is enforced from the
first commit rather than from the first time someone reads `CLAUDE.md`.
Runs **exactly once per vault**. It checks for prior runs and asks before continuing.
```
VAULT = {{VAULT_PATH}}
```
## The thing to get right
This vault has one invariant, and everything in it descends from that:
> The vault stores tracker **identity** (a URL) — never tracker **state**.
The most consequential question in this skill is therefore **which tracker owns execution**. If the
user has no tracker, that is a legitimate and complete answer (`tracker: none`) — it means the plan
slots stay in the vault, and the plan gate never fires. Do not push them toward adopting one.
Read `{{VAULT_PATH}}/CLAUDE.md` before you start. You are about to edit it.
## Procedure
### Step 1 — Check for prior initialization
Look for `.vault-meta.json` at the vault root.
If it exists: read it, tell the user when it was initialized and summarize the prior answers in one
line, then use `AskUserQuestion` to confirm a re-run — warning that prior personalization will be
overwritten. Continue only on yes. On a confirme