memory-map

Two-tier project memory system. Maintains a global Claude memory snapshot of all ongoing projects AND a per-project STATUS.md file in each project folder that captures last-session state, next actions, blockers, and key locations — so context survives long absences. Operates in two modes. WRITE mode triggers when the user says "save this", "memorise this", "snapshot this", "checkpoint [project]", "update your memory", "store this session", "remember all of this", or "save progress" — also proactively at the natural close of any productive session. READ mode triggers when the user says "where did I leave off", "catch me up on [project]", "restore context", "what was I doing", "[project] status", or returns to a project after a long gap. Works in both Claude Code (writes and reads STATUS.md directly in the project folder) and Claude.ai (updates global memory and emits STATUS.md content as an artifact for the user to save). Do not wait to be asked if a session was clearly productive.

Clean stale, outdated, or redundant entries from Claude's stored memory. Use this skill when the user says things like "clean up memory", "prune memory", "memory is getting cluttered", "remove old entries", "consolidate memory", or "trim the memory map". Also trigger proactively when memory approaches its limits — 30 entries on claude.ai, 200 lines on Claude Code — or when entries reference past events that have completed (an event date that has passed, a deliverable marked "upcoming" that is now shipped). Always propose changes for user confirmation before applying — never delete memory autonomously. Pairs with memory-map and memory-recall to form the complete memory loop.

Load and summarise stored project memory at the start of a session, or whenever the user asks what Claude remembers about their work. Use this skill when the user says things like "what do you remember", "what's the context", "where did we leave off", "catch me up", "what's the current state", "show me the memory map", or "what do you know about my projects". Also trigger proactively at the start of any new conversation if a memory store exists — surface the current state and pending items without being asked, so the user does not have to re-orient Claude. Pairs with memory-map (which writes memory) and memory-prune (which cleans it). Together they form a complete memory loop across Claude sessions.