/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 -y skills add evolution-foundation/evo-nexus --skill dev-remember --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/dev-remember
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
dev-remember.SKILL.mdname: dev-remember
description: 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.
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)
Read more
name: dev-remember description: 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.
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)
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

