a2wave-memory
SolidProgressively recall and maintain a2wave cross-session memory through a compact startup catalog, bounded topics, and searchable history.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- LilithGames
- Repository
- LilithGames/a2wave
- Created
- 2 weeks ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
using-memory
Use whenever you READ FROM or WRITE TO the agent-memory layer — recall a remembered fact, persist a durable fact about how the user wants to work, pin a hard rule, or correct a stored memory. READ via /ultra-memory:memory-recall (trusted CLI) or the type-scoped knowledge MCP; WRITE only through the memory verbs (/ultra-memory:memory-save, /ultra-memory:memory-pin, /ultra-memory:memory-verify, /ultra-memory:memory-edit, /ultra-memory:memory-inbox) — NEVER raw SQLite. Trigger before any memory read or write.
bettermemory
Verification-grade memory between sessions. Use bettermemory's MCP tools (memory_search, memory_show, memory_write, memory_verify, memory_record_use, etc.) instead of writing to files when the user asks you to "remember" something or references shared context from a past session. Default is to NOT call memory_search; only retrieve when the user references context you don't have ("my project", "the script we wrote") or a request is ambiguous in a way stored preferences could resolve. Every hit carries a staleness_verdict (calendar + path-drift + commit-drift); when it isn't "fresh", spot-check a claim before relying and call memory_verify to attest. Every use should record a claim_excerpt so retrievals stay auditable.
auto-memory
This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to structure memory files', 'MEMORY.md is too long', 'what goes in memory vs topic files', 'memory best practices', or wants to establish a persistent knowledge base across Claude Code sessions. Triggers on: memory setup, MEMORY.md, topic files, cross-session knowledge, persistent notes, memory maintenance, memory pruning.