Project Memory Store

Project Memory Store automatically extracts and categorizes insights—episodic events, procedural workflows, and semantic patterns—from your conversations and persists them in file-based memory under .claude/skills/project-memory-store. Invoke it after major decisions or discoveries using --project-store or --learn, or it triggers on critical learning signals like frustration, ensuring hard-won knowledge is available for future reference.

Use project memory for lasting, project-specific knowledge: debugging solutions, architecture decisions, integration patterns, and workflow discoveries that future team members or your future self will need. General notes capture temporary thoughts; project memory consolidates validated learnings into searchable, consolidated entries that prevent knowledge decay across tasks.

Intelligent consolidation merges new insights with existing knowledge, updating or generalizing entries to eliminate duplication and keep your memory lean. Entries are stored compactly (3–5 sentences max) and organized into episodic, procedural, and semantic categories, ensuring quick readability and preventing bloat as the structure evolves.

Memories are organized into three semantic categories—episodic (concrete events), procedural (workflows), and semantic (patterns)—within the .claude/skills/project-memory-store structure. The SKILL.md updates as your memory structure evolves, allowing you to track and retrieve insights by type and context across your projects.

Document the problem statement, failed attempts, final solution, and project-specific context that makes the solution unique. The Skill captures both successes and failures in 3–5 sentences, ensuring the next developer or future you has enough detail to apply the solution without re-solving the same issue.

Yes. Store architecture decisions, discovered patterns, integration workflows, and schema insights—any knowledge specific to your project's design or structure. The Skill consolidates these learnings across conversations, ensuring project-specific patterns and decisions are preserved and accessible when future tasks touch related code.