create-memory

Document architectural decisions and learnings by creating structured memory files in Markdown format under .claude/memory/. Memory files capture purpose, key learnings, implementation details, and common pitfalls—ensuring decisions persist and remain accessible for future reference and consistency across the project.

Track patterns and prevent knowledge loss by establishing a memory-file lifecycle: create files documenting significant learnings, update them as patterns evolve, and archive outdated entries. This structured approach ensures institutional knowledge persists and guides consistent implementation choices.

Yes. Memory files include a Related section that contextually links new memories to existing ones and relevant code files, creating a connected knowledge graph that shows how decisions, patterns, and learnings depend on and inform each other across the project.

Create a memory file when establishing new workflows, solving complex bugs with important learnings, implementing major features, or making architectural decisions. Memory files formalize knowledge that shapes future work; use them for decisions and patterns that recur, not one-off implementation notes.

Memory files integrate through a CLAUDE.md index file that imports and organizes all memories, creating a central knowledge hub. The fixed template—with Status, Date, Related, Purpose, Key Learnings, Implementation Details, Common Pitfalls, and Examples—ensures consistent structure and discoverability across your memory system.

Memory files follow a full lifecycle: creation for active learnings, updates as knowledge evolves, deprecation when patterns shift, and archiving when decisions no longer apply. This approach maintains a historical record while keeping the active memory set current and actionable.