setup

# /memory-kit:setup — adopt the kit in an existing repository The plugin ships behaviour; the repository owns the state. This skill creates that state — **always asking before the first write**, and never touching files the repo already has. Running without a user who can answer (a headless or `-p` run)? Then "offer" means **skip and report**: take the documented default where one exists, install nothing that the skill marks as opt-in, and finish with a list of what was deliberately not installed and what question is still open. Never invent a preference on the user's behalf and never present a skipped step as done. ## Step 0 — look before you write Report in two lines what already exists: `.claude/memory/MEMORY.md`, `context/handoffs/`, `knowledge/`, `projects/`, an existing documentation home (`docs/`, `doc/`, `documentation/`), `.claude/settings.json`, `.gitignore`, and whether this repo already holds work of its own — code, or documents other than a bare README (a real project) — or is effectively empty (a fresh memory workspace). Being a git repo decides nothing; content does. Everything after this is a proposal the user confirms once, not a sequence of prompts. ## Step 1 — the shared memory layers These four are shared across every project in the repo. Create only what is missing, copying from `${CLAUDE_PLUGIN_ROOT}/templates/`: | Path | From | Purpose | |---|---|---| | `.claude/memory/MEMORY.md` | `templates/MEMORY-TEMPLATE.md` | the hot cache the hook injects e...