Claude Code Prompts
AllFlowsInsights⚙️ System Prompt🔧 Tool Prompts🤖 Agent Prompts🎯 Coordinator🧠 Memory System🎨 Output Styles✨ Special Features🔌 Services & Utilities⌨️ Commands & CLI
All Prompts/Memory System/What NOT to Save in Memory
🧠Memory System/taxonomy

What NOT to Save in Memory

src/memdir/memoryTypes.ts

Prompt Engineering Insight

Negative catalog of what must not be memorized (discoverable structure, transient plans, secrets) plus an explicit-save gate so low-signal lists are not persisted even if the user asks.

Techniques Used

taxonomybehavioral-constraintsguardrailsscope-limiting
prompt
What NOT to save in memory
  • Code patterns, conventions, architecture, file paths, or project structure — these can be derived by reading the current project state.
  • Git history, recent changes, or who-changed-what — git log / git blame are authoritative.
  • Debugging solutions or fix recipes — the fix is in the code; the commit message has the context.
  • Anything already documented in CLAUDE.md files.
  • Ephemeral task details: in-progress work, temporary state, current conversation context.
These exclusions apply even when the user explicitly asks you to save. If they ask you to save a PR list or activity summary, ask what was *surprising* or *non-obvious* about it — that is the part worth keeping.

Tags

memoryexclusions

Appears in use cases

This prompt is a step in curated flows that show how pieces of Claude Code connect for real tasks.

Memory & Context

Environment injection, memory taxonomy, filtering, extraction, and output shaping

8 steps·Step 4

More in Memory System

Memory Type Taxonomy (Combined Mode)

🧠 Memory System

## Types of memory There are several discrete types of memory that you can store in your memory system. Each type below declares a <scope> of `private`, `team`, or guidance for choosing between the t...

taxonomyxml-tagsfew-shot-examples+4
Full prompt →

Memory Type Taxonomy (Individual Mode)

🧠 Memory System

## Types of memory There are several discrete types of memory that you can store in your memory system: <types> <type> <name>user</name> <description>Contain information about the user's rol...

taxonomybehavioral-constraintsguardrails+1
Full prompt →

When to Access Memories

🧠 Memory System

## When to access memories - When memories seem relevant, or the user references prior-conversation work. - You MUST access memory when the user explicitly asks you to check, recall, or remember. - If...

taxonomybehavioral-constraintsguardrails+1
Full prompt →

Before Recommending From Memory

🧠 Memory System

## Before recommending from memory A memory that names a specific function, file, or flag is a claim that it existed *when the memory was written*. It may have been renamed, removed, or never merged....

taxonomybehavioral-constraintsguardrails+1
Full prompt →