← ClaudeAtlas

setuplisted

First-time memory-loop setup — offer identity names, create HABITS.md from the template, write an initial config, and verify the hooks respond.
choiyounggi/groundwork · ★ 3 · AI & Automation · score 72
Install: claude install-skill choiyounggi/groundwork
# memory-loop: setup Walk the user through first-time setup, in this order. Every step is optional — respect a "skip". ## 1. Identity Run the `identity` skill flow: offer the one-time name setup (set or decline). See that skill for the schema and the confirmation rule. ## 2. HABITS.md The habit-distillation frame is two files — rules that load every session, and the case records they point to, which do not: ``` ~/.claude/groundwork/HABITS.md (imported into every session) ~/.claude/groundwork/HABITS-CASES.md (on demand, via [Cnn] pointers) ``` - If they do not exist, copy the templates: ```bash mkdir -p ~/.claude/groundwork cp "${CLAUDE_PLUGIN_ROOT}/templates/HABITS.md" ~/.claude/groundwork/HABITS.md cp "${CLAUDE_PLUGIN_ROOT}/templates/HABITS-CASES.md" ~/.claude/groundwork/HABITS-CASES.md ``` - If either already exists, **never overwrite it** — it holds the user's accumulated habits. Because of that, re-running this step is also the migration path for a HABITS.md that predates the two-file layout: the cases file gets created, the habit file is left exactly as it is. (The `habit` skill describes how to move the prose across.) - Then *suggest* (do not apply) adding an import line to the user's own `~/.claude/CLAUDE.md` so the habits load into every session — show them the exact line and let them add it: ``` @groundwork/HABITS.md ``` (The path is relative to `~/.claude/`. Never edit the user's CLAUDE.md yourself.) Import **only** H