dev-remember

Persist structured engineering notes with title, context, and reference fields.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-remember
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-remember
Source: https://github.com/EvolutionAPI/evo-nexus/tree/main/.claude/skills/dev-remember
Command: npx skills add https://github.com/EvolutionAPI/evo-nexus --skill dev-remember

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineers often make small but important decisions, discover gotchas, or confirm patterns during a session that need to survive beyond the immediate conversation but do not warrant a full long-term memory entry. Dev Remember provides a lightweight, structured way to capture those short-term engineering notes so future sessions and agents can recall them.

Core Features & Use Cases

  • Quick persistence: Capture one-line titles with short context so important decisions are not lost between sessions.
  • Structured note format: Encourage Title, Why this matters, Context, and Reference fields to make notes searchable and actionable.
  • Agent-targeted storage: Store notes in agent-specific memory folders or workspace development paths for easy retrieval by the relevant engineering agents.
  • Use Case: Save a discovered compatibility issue ("lib v3 breaks auth") with context and a commit reference so the next debugging session avoids redundant investigation.

Quick Start

Save a short engineering note titled "Avoid v3 auth regression" explaining why it matters, when it applies, and include a reference commit or file:line.

Frequently Asked Questions about dev-remember

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist engineering decisions and gotchas between coding sessions?▼

To persist engineering decisions between sessions, capture short-term notes using structured fields like title, context, and reference, then store them in agent-specific memory folders for later retrieval.

What is the best way to save short-term debugging context for future agent retrieval?▼

Saving short-term debugging context requires storing quick notes with structured fields—title, why this matters, context, and reference—in workspace development paths so engineering agents can retrieve them later.

Can I save granular engineering patterns without using long-term shared memory?▼

Yes, you can save granular engineering patterns without long-term shared memory by using lightweight, structured notes stored in agent-specific memory folders designed for short-term session context.

How do I structure engineering notes to make them searchable for future debugging?▼

Structure engineering notes for searchability by including four fields: a concise Title, Why this matters, Context, and a Reference like a commit hash or file:line to ensure actionable retrieval.

When do I need to track engineering decisions across separate agent conversations?▼

Track engineering decisions across conversations when you discover compatibility issues, confirm test idioms, or identify patterns too granular for long-term memory but critical enough to survive beyond the immediate session.

Does saving session context require dependencies or external components?▼

Saving session context requires no external dependencies or components, relying solely on structured note fields stored directly in agent-specific memory folders or workspace development notes.