← ClaudeAtlas

session-continuitylisted

Establish and maintain cross-session memory for a project via two in-repo docs — .session-continuity/SESSION_PRIMER.md (current state, refreshed alongside substantive commits) and .session-continuity/LEARNINGS.md (append-only wisdom for 15+ min bugs). Use when starting, before commits, or after hard-won bugs.
talgolan/session-continuity · ★ 0 · Web & Frontend · score 70
Install: claude install-skill talgolan/session-continuity
# Session Continuity Two in-repo files act as a handoff between Claude sessions on the same project: - **`.session-continuity/SESSION_PRIMER.md`** — current-state snapshot (latest commits, outstanding items, test counts, workflow conventions). **Refresh alongside substantive commits** (stage the update in the same commit as the real change). Always reflects "what's true right now." - **`.session-continuity/LEARNINGS.md`** — accumulated wisdom (numbered entries, grouped by layer). Append-only log of bugs that were painful enough to not want to rediscover. **Update when a bug takes 15+ minutes to diagnose.** The two files are complementary: primer is volatile current-state, LEARNINGS is durable wisdom. A fresh session reads the primer first to get oriented, then consults LEARNINGS when something surprising happens. If installed as a plugin, three commands are available: `/session-continuity:primer` (init/refresh/check the primer), `/session-continuity:learning` (append a new LEARNINGS entry interactively), and `/session-continuity:end-session` (close-out ritual — refresh the primer, capture any new learnings from this session, and report a ✓/⚠️ checklist before you close the laptop). Hooks in `hooks/hooks.json` remind Claude to read the primer on session start and nudge when a `git commit` lands without a primer refresh staged. ## When to use this skill Invoke when: - Starting work on a project that does not yet have `.session-continuity/SESSION_PRIMER.md` and `.session-