Session 1 · The mess
Three tasks, one chat
You build. You add a feature. You restyle. Nobody told you those were three tasks — boundaries are invisible while you're inside them.
🔨Built it — a working habit tracker, one prompt, one file.
➕Added a feature — add & delete habits, with a confirm.
🎨Restyled it — rounder cards, bolder button, a 🔥 on hot streaks.
→ run /context — the chat is heavy with all three jobs
…quit Claude Code, reopen, and ask:
Add a stats panel showing my best streak.
Claude: "Which app do you mean? I don't see
any project context here…"
The chat was your project's only memory — and you just lost it.
Everything Claude knew lived in the conversation. Close it, lose it.
Session 2 · Give it a memory
Files remember. Chats don't.
1Run /init → CLAUDE.mdHow we work — how to run it, how to verify it, style rules, gotchas. Read automatically, every session.
2Create ROADMAP.mdWhat we're building — checkboxes: Done · Next · Someday. A task = one checkbox.
3Wire them togetherAdd to CLAUDE.md: "ROADMAP.md is the plan of record — read it before any work, check off only what's verified."
/clear — wipe everything, on purpose
Read CLAUDE.md and ROADMAP.md, then tell me
where the project stands and what's next.
Claude: "Core tracker, habit management and
polish are done. Next up: the 7-day history
grid…" ← it lost NOTHING.
Chat is RAM. Files are disk.
Session 1's invisible tasks are now three checked boxes. You don't find boundaries — you draw them.
Session 3 · The long task
Mid-task? Compact, don't clear.
The history grid hits a date bug. The chat gets long — but the whole bug hunt lives in the chat. Clear now and you lose the trail.
🔍Check the meter — /context shows what's filling the window.
🗜️Not at a checkbox → compact — the thread survives, the junk goes.
🩸Bug fixed → gotcha to CLAUDE.md — so it never costs you twenty minutes again.
/compact focus on the day-boundary bug:
what we tried and what's still broken
…fix it, verify it, then the ritual:
It works. Check off the history grid in
ROADMAP.md, and add a gotcha to CLAUDE.md:
day keys are local YYYY-MM-DD strings —
never use toISOString() or UTC for dates.
/clear
Long chat but unfinished task → compact. Finished checkbox → clear.
Session 4 · The payoff
The second time you say it, write it down
The stats panel is the fastest session yet — because the files are doing the remembering.
✨Unprompted — Claude uses the local-date rule from CLAUDE.md without being told. Straight through a /clear.
📚It suggests a chart library — you've said "no libraries" once before. That's the trigger.
No libraries. And add to CLAUDE.md:
single file, no frameworks, no external
libraries — ever.
Rule of thumb: the second time you'd have
to tell Claude something — stop telling it.
Put it in the file.
CLAUDE.md is compound interest.
CLAUDE.md survives /clear and /compact — it re-loads from disk every time.
Session 5 · The cautionary tale
The mistake isn't clearing — it's clearing without saving
1Halfway through dark mode… /clearNo checkpoint, no roadmap update. (On purpose — watch what happens.)
2"Continue the dark mode work"The new session flounders — which colors? what's half-done? It starts a conflicting approach.
3The safety net: /resumeClear doesn't shred the old session — pick it back up, finish properly, then do the ritual.
What got lost was only ever in the chat:
the colors we picked, the half-done state.
The roadmap still said "not done" — but the
decisions were written nowhere.
Clear only at a checkbox.
/resume is a safety net — not a strategy.
Stage this once for yourself — losing work on purpose teaches faster than any rule.
Session 6 · The habit
Make it a habit
1Open on the files"Read CLAUDE.md and ROADMAP.md, then build the next item: …"
2Build one checkboxOne task per session. Compact if it runs long.
3Verify it yourselfExport → delete a habit → import → it's back. Outcome, not claim.
4Check off · gotchas to CLAUDE.md · /clearFive beats. Boring on purpose. That's what a habit feels like.
/memory — everything Claude loads each
session. Your whole external brain.
Auto-compact kicks in near the limit —
the skill is doing it on purpose, earlier,
at the moment YOU choose.
The roadmap outlives every session.
Compare /context from Session 1 to now — lean, focused, cheap.
The takeaway · steal this ritual
Clear at a checkbox. Compact in the middle. Disk remembers.
THE CONTEXT RITUAL — one app, many sessions
DRAW THE LINES → ROADMAP.md with checkboxes. A task = one checkbox.
START EVERY SESSION → "Read CLAUDE.md and ROADMAP.md, then build the next item: …"
MID-TASK, CHAT HEAVY? → /context to check · /compact focus on <what you're fixing>
CHECKBOX DONE? → verify it → check it off → gotchas to CLAUDE.md → /clear
SECOND TIME you tell Claude something → it goes in CLAUDE.md
SLIPPED? → /resume brings the old session back
The boundary test: could a brand-new teammate pick up the next piece of work from just the files?
✅Yes — you're at a boundary. Checkpoint & /clear.
🚧No — you're mid-task. Keep going, or /compact.
Replay the whole build — every prompt is in the pack under this lesson.
← Back to course