← ClaudeAtlas

save-sessionlisted

MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands — also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.
faizkhairi/claude-code-blueprint · ★ 25 · AI & Automation · score 81
Install: claude install-skill faizkhairi/claude-code-blueprint
**Prerequisite check (run first)**: if `./memory/` does not exist OR `~/.claude/.memory-disabled` marker file is present, this skill is a no-op. Output: "Memory persistence is disabled. Run `./setup.sh` and choose to enable memory if you want this skill to work." Save session state to memory: 1. **Update session.md** at `./memory/core/session.md`: - Current topic and what we're working on - Recent progress (what was accomplished this session) - Next steps (what should happen next session) - Any blockers or open questions 2. **Update reminders** at `./memory/core/reminders.md`: - Ask the user if there are any pending tasks, deadlines, or reminders to carry forward - Remove completed reminders (move to Completed section with date), keep active ones, add new ones 3. **Update per-project context**: If working on a registered project, update `./memory/projects/active/{project}.md` → Session Context section: - Last worked on (what specifically) - In progress (current state) - Next up (what should happen next on THIS project) 4. **Check preferences.md**: If new preferences or work patterns were observed during this session, update `./memory/core/preferences.md` 5. **Check MEMORY.md**: If new technical learnings or gotchas were discovered, update `{MEMORY_MD_PATH}`. After any edit, count total lines — if over 170, warn that MEMORY.md is approaching the 200-line auto-truncation limit and suggest moving content to topic files. 6. **Check decisions.md**