dev-remember
Persist context across engineering sessions — save important decisions, gotchas, or patterns that should survive beyond the current conversation. For long-term workspace memory, prefer mempalace.
适合你，如果常因切换会话丢失上下文
npx oh-my-skill add evolution-foundation/evo-nexus/dev-remembercurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- evolution-foundation/evo-nexus/dev-remembernpx oh-my-skill verify evolution-foundation/evo-nexus/dev-remember怎么用
商店整理自技能原文 · 版本 7f5dd76 · 表述以原文为准Claude 能快速保存工程会话中的关键决策、陷阱或模式，并跨会话记忆。笔记存入对应代理的内存文件夹或研究笔记中，确保下次会话可用。
当你做出非显而易见的决策、发现陷阱（如库版本破坏认证）、确认模式（如模块统一用 Result<T>），或需要为下次会话快速记笔记时触发。不适用于已由代理内存覆盖、共享知识或仅当前会话的信息。
技能原文 SKILL.md
Dev Remember
Derived from oh-my-claudecode (MIT, Yeachan Heo). Adapted for the EvoNexus Engineering Layer.
Quick context persistence for engineering sessions. Save decisions, gotchas, or patterns that should survive the current conversation but don't deserve a full memory entry in mempalace.
Use When
- A non-obvious decision was made that future-you needs to remember
- A gotcha was discovered (e.g., "this lib's v3 silently breaks auth")
- A pattern was confirmed (e.g., "we always use Result<T> not exceptions in this module")
- Quick "remember this for next session" notes
Do Not Use When
- The note is already covered by an agent's memory folder → write to
.claude/agent-memory/{agent}/instead - The note is shared workspace knowledge → write to
memory/(mempalace owns this) - The note is ephemeral (current conversation only) → don't persist it
Storage Location
Engineering layer notes go to the relevant agent's memory folder:
- Architecture decision →
.claude/agent-memory/apex-architect/ - Bug pattern →
.claude/agent-memory/hawk-debugger/ - Test idiom →
.claude/agent-memory/grid-tester/ - etc.
If the note doesn't fit any single agent, save to workspace/development/research/[C]remember-{topic}-{date}.md.
Format
Each note has:
- Title (1 line)
- Why this matters (1-2 sentences)
- Context (when does this apply?)
- Reference (file:line, commit, or external link)
Mempalace Note
For long-term, cross-session, cross-agent shared memory, prefer mempalace:
- It has structured drawers, rooms, and wings
- It supports knowledge graph queries
- It survives across sessions natively
dev-remember is for engineering-specific quick saves. mempalace is for everything else.
Pairs With
- All 19 engineering agents (each has its own memory folder)
- mempalace (for shared workspace memory)
prod-memory-management(the Clawdia skill that owns shared memory)