Save Decisions and Discoveries to Memory
Save discoveries and decisions to existing memory with scope, rationale, timestamps, and verified readback.
Before & after
Same prompt, same agent — the only difference is the skill.
Got it — your staging database resets every night at 2am UTC. I'll keep that in mind for our conversation. Note that I don't have persistent memory across separate sessions unless you're using a tool that provides it, so you may want to document this somewhere permanent like a team wiki or runbook if it's important for others to know. Is there anything else you'd like me to remember for now?
SAVED TO MEMORY
Fact: Staging DB resets nightly at 2am UTC.
Saved: 2026-07-31 14:20 UTC
Context: flagged during a debugging session — explains why test data
vanishes overnight and why a 1am-run seed is gone by morning.
Tags: staging, database, gotcha
WHY THIS WAS SAVED EXPLICITLY
Auto-capture catches a lot, but a fact like this — load-bearing, easy to
forget, expensive when forgotten — is worth a deliberate save with a
timestamp and the reason it mattered. Six weeks from now the timestamp
and context are what make it trustworthy: you'll know when it was true
and why it was written.
IT WILL SURFACE WHEN RELEVANT
Next time a "my test data disappeared" or "staging is empty" situation
comes up, this note surfaces with its context, so the 2am reset gets
ruled in immediately instead of rediscovered.
Anything to add — like who owns the reset job, in case it needs
changing?About this skill
“Remember this” should leave behind something the next session can actually use. This captures the exact discovery or decision, explains when it applies, and saves it into the existing memory system without introducing contradictory notes or invented context.
What it does
- Turns a conversation into atomic memory entries with a fact or decision, scope, rationale, source, and timestamp.
- Distinguishes user-reported facts, directly observed evidence, and unverified explanations.
- Finds the existing memory destination and preserves its format instead of creating a competing system.
- Updates duplicate entries and explicitly supersedes stale claims while preserving unrelated knowledge.
- Reads back saved changes and distinguishes a verified save from a draft that could not be persisted.
- Captures conditions that would invalidate a note so temporary blockers do not become permanent rules.
What you get
A durable memory entry saved and read back when memory access is available, plus a concise confirmation of its scope and destination. Without write access, you get the exact proposed entry and a clear statement that it remains unsaved.
Best for
Developers and technical teams using Claude Code or Claude who need important bug discoveries, project decisions, constraints, and recurring preferences to survive beyond the current conversation.
SKILL.md preview
---
name: save-decisions-and-discoveries-to-memory
description: Explicitly save important discoveries, decisions, and preferences into the existing memory system using atomic entries with scope, rationale, source, timestamps, conflict resolution, and readback verification. Use when the user says "remember this", "don't forget this decision", "save this for next time", "we keep rediscovering this bug", "my next session keeps forgetting this", "update what you remember about this", or "make sure this survives the session".
---
# Save Decisions and Discoveries to Memory
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.