The user wants to save this to long-term memory: $ARGUMENTS
Quick start
memory_save {
"content": "We rotate JWT refresh tokens on every use; the old token is revoked server-side in auth/refresh.ts.",
"concepts": "jwt-refresh-rotation, token-revocation, auth-flow",
"files": "src/auth/refresh.ts"
}Expected output:
Saved memory abc12345 with 3 concepts: jwt-refresh-rotation, token-revocation, auth-flow.Why
A memory is only as useful as the terms that retrieve it. Tag with specific concepts so a future recall finds it, and preserve the user's own phrasing.
Workflow
- Pull the core insight, decision, or fact out of
$ARGUMENTS. - Extract 2-5 lowercased concept phrases. Prefer specific over generic
(jwt-refresh-rotation beats auth).
- Extract referenced file paths (absolute or repo-relative). Empty if none.
- Call
memory_savewithcontent,concepts(comma-separated string), and
files (comma-separated string).
- Confirm the save and echo the concepts so the user knows the retrieval terms.
Anti-patterns
WRONG: concepts: "stuff, code, notes" (generic tags nothing can find later).
RIGHT: concepts: "jwt-refresh-rotation, token-revocation" (specific, retrievable).
Checklist
- Content preserves the user's phrasing, not a paraphrase.
- Concepts are specific, lowercased, 2-5 items.
- File paths are real references, not guesses.
- Confirmation echoes the exact concepts tagged.
See also
recall: retrieve what you save here (the pair to this skill).forget: remove a memory you saved by mistake.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if memory_save is not available.
