← ClaudeAtlas

memory-maplisted

Two-tier project memory: a global cross-project index plus a STATUS.md in each project folder (last session, next actions, blockers, key locations), so context survives long absences. WRITE mode triggers on "save this", "memorise this", "snapshot this", "checkpoint [project]", "update your memory", "store this session", "remember all of this", or "save progress", and proactively at the natural close of any productive session; do not wait to be asked. READ mode restores ONE project from its STATUS.md: "catch me up on [project]", "[project] status", "restore context", or returning to a project after a long gap. "Where did I/we leave off" and "what was I doing" trigger READ mode only when a project is named or the current folder has a STATUS.md. For a cross-project overview ("what do you remember", "show me the memory map"), use memory-recall instead.
shandar/memory-map · ★ 2 · AI & Automation · score 75
Install: claude install-skill shandar/memory-map
# Memory Map Skill — v0.2 A two-tier project memory protocol for context that survives long absences. ## The model Two layers, each with a distinct job: | Tier | Where it lives | What it stores | Scope | |------|----------------|----------------|-------| | **Global** | claude.ai: memory API (`memory_user_edits`) · Claude Code: `~/.claude/memory.md` | Cross-project index + state snapshot | ~30 entries (claude.ai) · under 200 lines (Claude Code) | | **Per-project** | `<project>/STATUS.md` | Deep state for one project | Unlimited, one per repo | Global memory answers: *what am I working on across everything?* STATUS.md answers: *where exactly did I leave off in this one project?* Read together, they restore full context. Written together, they stay in sync. --- ## Two modes Identify the mode before doing anything else. ### WRITE mode — save state Triggered when: - User asks to save: "save this", "memorise this", "snapshot", "checkpoint [project]" - User asks to update: "update memory", "store this session", "remember all of this" - Session naturally closes after productive work (proactive trigger) - PWP phase transition mentioned ("plan done, moving to execute" → update phase tag) ### READ mode — restore context Triggered when: - User asks for orientation about one project: "catch me up on [project]", "restore context", or "where did I leave off" / "what was I doing" when a project is named or the cwd has a STATUS.md - User asks for status: "[project] status", "