Agent skill · writing content · jeremylongshore
memory
Execute extract and use project memories from previous sessions for
Why this skill is useful
Adds a persistent memory management system that allows the AI to recall and apply user preferences and project conventions automatically across sessions.
What it needs
Requires claude-never-forgets installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Memory Overview Memory provides persistent context across Claude Code sessions by storing and retrieving project decisions, user preferences, and coding conventions from a local JSON file. When a new session starts, stored memories load automatically so previously established patterns carry forward without re-explanation. Prerequisites Project memory file at .claude/memories/projectmemory.json (created automatically on first memory save) Read and Write permissions for the .claude/memories/ directory Claude Never Forgets plugin installed (/plugin install yldrmahmet/claude-never-forgets) Instructions 1. Access stored memories. On session start, locate and read the memory file at .claude/memories/projectmemory.json using the Read tool. Parse the JSON structure containing timestamped memory entries. See ${CLAUDESKILLDIR}/references/implementation.md for the full retrieval workflow. 2. Match memories to current context. Scan memory entries for keywords and topics relevant to the current task. Extract applicable decisions (e.g., "use pnpm instead of npm"), architectural patterns, library choices, and coding style preferences. 3. Apply memories silently. Incorporate remembered preferences into responses and tool usage without announcing them. When a memory dictates a package manager, testing framework, or naming convention, follow it automatically. 4. Store new memories. When significant decisions occur -- library selections, architectural choices, user-stated preferences, or tool rejections -- write them to the memory file with a timestamp. Add entries via the /remember command or through automatic capture of conversation signals. 5. Resolve conflicts. When a stored memory contradicts a current explicit request, prioritize the current request. Flag the conflict if appropriate and update the memory entry to reflect the new decision. Remove outdated memories that no longer apply. 6. Handle cleanup. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/memory