Member-only story
Build a Project Knowledge Base for Claude Code
Use CLAUDE.md for instructions, Auto Memory for recurring learnings and a source-linked wiki for knowledge you want to reuse across projects.
When Open Claude Code in a fresh session and the conversation starts with a new context window. It may need to inspect the repository and reconstruct what changed. That can feel like starting over.
But Claude Code has no memory is no longer correct. Claude Code has project instructions in CLAUDE.md and an Auto Memory feature that can carry selected learnings between sessions.
Those solve useful problems. They do not automatically become a durable, cross-project research library or a reviewed record of every architectural decision.
If you hit the paywall, use the friend link here: read the full post.
That distinction is where a Markdown wiki can help.
The useful question is not “Should we replace Claude Code memory with a wiki?” It is: what knowledge needs to persist, who should maintain it and how should the agent retrieve it?
Three kinds of memory are easy to confuse
CLAUDE.md is best treated as instructions: how to build, test and work in this repository. Anthropic recommends putting repeated corrections and project…
