If you’ve been working in a Claude for a while - it has built for you a project-scoped memory. And quite often it looks like a bloated file with wrong decisions and statements, and outdated rules that you may have told it in the past and long ago forgot about. If you experience weird behavior or unexpectedly high usage, try this prompt: Review, refactor and clean up this project’s auto-memory. Read the memory index (MEMORY.md) and every memory file. Check each claim against the project itself: code, config, instruction and doc files, and git history. Trust the project over memory. Put each memory in one class:
- Contradicts: conflicts with the project, another memory, or itself.
- Stale: finished work, past dates or deadlines, things that no longer exist, old versions or counts.
- Duplicate: the project already records it.
- Bloated: the same fact repeated, or old paragraphs later superseded in the same file.
- Keep: a current, non-obvious decision or trap recorded nowhere else. Also check:
- every index line points to an existing file and matches that file’s description;
- frontmatter is valid (name, description, metadata.type);
- no orphan files missing from the index. Report one table per class (memory, problem, change). List the questions only I can answer. Change nothing yet. After I approve:
- archive removed files to a sibling memory-archive-YYYY-MM-DD/ folder, never delete them;
- fix or trim what stays;
- rewrite superseded text in place instead of appending another dated note;
- update the index (one line per memory);
- record my answers in the matching memory with today’s date. Finally, list any fact that lived only in removed memories and that the project doesn’t record. Suggest where each should go. Be terse. Use tables, and file:line evidence for every claim. submitted by /u/dr-dimitru
Originally posted by u/dr-dimitru on r/ClaudeCode
You must log in or # to comment.