claude-code-source-map

/**
 * Create a memoized system prompt section.
 * Computed once, cached until /clear or /compact.
 */
export function systemPromptSection(name, compute) {
  return { name, compute, cacheBreak: false }
}

/**
 * Create a volatile system prompt section that recomputes every turn.
 * This WILL break the prompt cache when the value changes.
 * Requires a reason explaining why cache-breaking is necessary.
 */
export function DANGEROUS_uncachedSystemPromptSection(name, compute, _reason) {
  return { name, compute, cacheBreak: true }
}

Your ONLY task is to use the Edit tool to update the documentation file if there is substantial new information to add, then stop.

CRITICAL RULES FOR EDITING:
- Keep the document CURRENT with the latest state of the codebase - this is NOT a changelog or history
- Update information IN-PLACE to reflect the current state - do NOT append historical notes or track changes over time
- Remove or replace outdated information rather than adding "Previously..." or "Updated to..." notes
- Clean up or DELETE sections that are no longer relevant

DOCUMENTATION PHILOSOPHY - READ CAREFULLY:
- BE TERSE. High signal only. No filler wo…

Saving a memory is a two-step process:

Step 1 - write the memory to its own file in the chosen directory (private or team, per the type's scope guidance) using this frontmatter format: ...

Step 2 - add a pointer to that file in the same directory's MEMORY.md. Each entry should be one line, under ~150 characters: - [Title](file.md) - one-line hook. They have no frontmatter. Never write memory content directly into a MEMORY.md.

- Organize memory semantically by topic, not chronologically
- Update or remove memories that turn out to be wrong or outdated
- Do not write duplicate memories. First check if there is an existing memory you can update.