You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/tour/SKILL.md
+25-5Lines changed: 25 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,9 +29,11 @@ An interactive walkthrough where you teach the user the Memory Kit by working wi
29
29
30
30
Run in order for a full tour. Each step: **Pain → Read actual files → Do something → Confirm it worked.**
31
31
32
-
### Step 1: Memory
32
+
### Step 1: Memory — Two Tiers
33
33
**Pain:** Without this, I forget everything between sessions. Your name, decisions, preferences — gone.
34
-
- Read `.claude/memory/MEMORY.md` — show it, explain the structure you see (date convention, sections, topic files if any)
34
+
- Read `.claude/memory/MEMORY.md` — show it, explain the structure (date convention `[YYYY-MM]`, sections, 200-line cap)
35
+
- Read `.claude/memory/knowledge/index.md` — explain this is the wiki layer (concepts, connections, meetings, qa) loaded on-demand, not every session
36
+
- Explain the split: MEMORY.md = hot cache (one-line patterns, auto-loaded), knowledge/ = deep articles (Markdown + `[[wikilinks]]`, Obsidian-compatible but Obsidian NOT required)
35
37
- Ask the user for something to remember (stack, preference, convention)
36
38
- Write it to MEMORY.md in the format the file already uses
37
39
- Show the result
@@ -45,19 +47,37 @@ Run in order for a full tour. Each step: **Pain → Read actual files → Do som
45
47
46
48
### Step 3: Context Protection (Hooks)
47
49
**Pain:** Long conversations get compressed by Claude Code. Without protection, progress disappears mid-session.
48
-
- Read the 3 hook scripts in `.claude/hooks/` — explain what each one does IN PLAIN WORDS based on what you see in the code
50
+
- Read the 5 hook scripts in `.claude/hooks/` — explain each one IN PLAIN WORDS based on what you see in the code:
51
+
-`session-start.sh` — context overview at session start
52
+
-`pre-compact.sh` — BLOCKS `/compact` until MEMORY.md is updated (mtime check)
53
+
-`periodic-save.sh` — auto-checkpoint every 50 exchanges (configurable via `CLAUDE_SAVE_INTERVAL`)
54
+
-`session-end.sh` — auto-captures conversation transcripts to `daily/YYYY-MM-DD.md` in background (spawns `flush.py`)
55
+
-`protect-tests.sh` — blocks edits to existing test files (Write new tests allowed)
56
+
- Show `daily/` directory — explain that each session gets its own file, auto-written by the session-end hook, zero user action needed
49
57
- Reference the session-start output if it fired this session
50
58
- Key message: all automatic, user does nothing. Say "save context" to force a manual save anytime.
51
59
52
60
### Check-in
53
-
Ask: "That's the core. Want to see Rulesand Experiments too, or start working?" Steps 4-5 are optional.
61
+
Ask: "That's the core. Want to see Rules, Scripts pipeline, and Experiments too, or start working?" Steps 4-6 are optional.
54
62
55
63
### Step 4: Rules
56
64
**Pain:** If I make the same mistake twice, it's because nobody wrote it down.
57
65
- Show `.claude/rules/` — read any existing rules, explain what they do
58
66
- Offer to create one if the user has a convention. If not: "Say 'make this a rule' anytime I repeat a mistake."
59
67
60
-
### Step 5: Experiments
68
+
### Step 5: Memory Kit v2 Scripts (power user)
69
+
**Pain:** After 50 sessions, `daily/` has hundreds of entries — useful, but too raw to search efficiently.
70
+
- Show `.claude/memory/scripts/` — list the 5 files: `compile.py`, `lint.py`, `query.py`, `flush.py`, `config.py`
71
+
- Explain in one sentence each:
72
+
-`compile.py` — reads `daily/` logs and writes structured wiki articles into `knowledge/` (via `claude -p` subscription, zero API cost)
73
+
-`lint.py` — 7 structural health checks on `knowledge/` + `--fix` auto-repairs broken backlinks
74
+
-`query.py` — index-guided retrieval across `knowledge/`, with optional `--file-back` to save answers as Q&A articles (compounding loop)
75
+
-`flush.py` — called by `session-end.sh` hook in background; user never invokes manually
76
+
-`config.py` — path constants (don't touch)
77
+
- Demo: run `python3 .claude/memory/scripts/lint.py` against the empty wiki — show the output (likely 0 errors on a fresh clone)
78
+
- Key message: scripts are OPT-IN. Only `flush.py` runs automatically (via hook). The rest you call when you want to compile/query/lint. Pure Python stdlib, zero `pip install`.
79
+
80
+
### Step 6: Experiments
61
81
**Pain:** Sometimes you need to research before building. Without a sandbox, research and production code mix.
62
82
- Show `experiments/` — read README.md, explain the lifecycle based on what the file says
63
83
- Offer to create one if the user has an open question. If not: "Say 'create an experiment' when you hit a fork."
0 commit comments