claude-session-continuity
Memory for a tool that forgets everything.
Claude Code starts every session blank. These custom skills give it a durable cross-session memory, so "what was I doing?" takes ten seconds instead of ten minutes.
~/projects $ /wrapup Saved handoff to Session Diary/Portfolio.md + 1 rollup line to _Overall.md # next morning, cold start, zero memory ~/projects $ /catchup Good morning. Yesterday you shipped the hero section and stopped at the timeline. Next step: wire the scroll reveals. Plan for today ready.
Four slash-command skills over one central Session Diary: /wrapup checkpoints a session into a structured handoff, /catchup rebuilds context next time, /catchup-all briefs across every project from a one-line-per-session rollup, /checkin is the accountability variant. A fixed entry schema is the contract between the session that writes and the session that reads.
- Claude Code skills + hooks
- schema as contract
- context engineering
- documentation systems
living system
What it actually took. This came from genuine pain: a dozen projects in one folder and every morning spent re-explaining myself to a goldfish. The design goal became a sentence I kept testing against: a future session with no memory should be productive in ten seconds. Getting the entry format right mattered more than any code, because the reader is an AI with no context and no patience. I run it hourly, every day.