by Matt Corbett
Memory engineering team — agents (memory-architect-lead, memory-retention-and-erasure-engineer, memory-eval-cost-analyst) for the decisions behind a durable memory store: what earns a write, which paradigm, which surface holds the bytes, what makes it forget, what a delete leaves behind, cost per correct answer. skills, commands, dated knowledge files, best-practices, templates, scenarios, an advisory hook, a stdlib calculator. Advisory only — it never reads or mutates a real store. Seams: ai-agent-engineering decides whether an agent should remember at all and where state sits in its topology, this engineers the memory system itself; ai-red-teaming owns the ASI06 attack taxonomy and offensive testing, this owns the defensive design half; data-governance-privacy owns DSAR and legal basis, this owns erasure residue in embeddings and version history; retrieval → ai-rag-engineering; evals → llm-evaluation-engineering; the Claude app → claude-app-engineering. Requires ravenclaude-core@>=0.238.0.
Claude Code6 Skills