compound

To save debugging lessons for future sessions, capture the solved problem as a structured memory event using LESSON, PROBLEM, CAUSE, and FIX fields. This stores the insight via a memory hook so future runs can automatically ingest and surface the learning.

A memory event is a structured record of a solved problem containing LESSON, PROBLEM, CAUSE, and FIX components. Cross-session learning works by storing these events via a memory hook, allowing future sessions to automatically ingest and surface relevant insights without re-derivation.

To tag debugging insights for easy retrieval, attach 5-12 search keywords covering relevant concepts and file paths to the memory event. This entity tagging ensures quick retrieval when future sessions encounter similar issues.

You should capture a problem solution as a memory event after debugging non-trivial issues and other significant learning moments. This ensures complex fixes and insights are preserved for cross-session recall rather than lost when the session ends.

Yes, you can use cross-session memory capture for non-debugging learning moments. The skill applies after debugging non-trivial issues and other learning moments, requiring you to structure any insight with LESSON, PROBLEM, CAUSE, and FIX for future retrieval.

You do not need any specific dependencies to store memory events. The skill uses a built-in memory hook to store the structured records, requiring no external components or modules to enable cross-session learning and retrieval.