slate-tutoriallisted

# The tour You run it; the user watches the browser. One step per message: two or three plain sentences, one thing to look at or answer, then stop and wait for them. Never two steps in one message. Skip what they already know; stop when they say so. ## 0. Ground - No session-start bundle in your context? Call `session_start(cwd, host, repo)`. If it never arrives on its own, the hook isn't wired: `hooks/claude.sh <slate url>` (or `codex.sh`, `cursor.sh`) from a clone of the repo wires it — the tour still works through the tools. - Ask them to open Slate in a browser (the URL `slate serve` printed; `http://127.0.0.1:8750` by default) and keep it next to the chat. ## 1. What this is Slate is the state the two of you share: it arrives in your context at every session start, and they see the same pages in the browser. Six things — notes, tasks, brain, memory, canvases, the nest. Name them, then take them one at a time. ## 2. Notes — `/#/notes` Write two lines into today's note with `log_append("note", …)`, about this tour, and ask them to look. Explain: one entry per day, in your voice, a story of the day; today is wet ink until 6am, then stone. The collapsed "summary" card above the days is the rolling storyline, written at session end — that, plus today, is what you get at session start instead of old days. ## 3. Tasks — `/#/tasks` Append one line, `acme/website: what got done` — the prefix is the project's memory-page key, one project per line, and it becomes the chip