Distill Memory
Save durable insights to Nowledge Mem autonomously. Don't wait to be asked — save proactively when the conversation produces a durable fact, preference, decision, plan, procedure, learning, event, or important context.
When to Save
Save proactively when the conversation produces:
- A fact (durable reference detail, tool constraint, environment fact)
- A decision (architecture choice, tool selection, process change)
- A preference (code style, workflow, tool configuration)
- A plan (multi-step task design, roadmap item)
- A procedure (how to set up, how to debug, how to deploy)
- A learning (bug root cause, pitfall discovered, pattern recognized)
- An event (meeting outcome, release milestone, incident timeline)
- Important context (project background, stakeholder constraint)
Usage
Primary (MCP):
mcp__nowledge-mem__add_memory
content: "<what was decided or learned>"
title: "<short descriptive title>"
unit_type: "fact|preference|decision|plan|procedure|learning|context|event"
importance: 0.3-1.0
tags: ["<relevant tags>"]
Fallback (CLI):
nmem --json m add "JWT refresh failures came from clock skew." \
--title "JWT refresh failures traced to clock skew" \
--importance 0.9 --unit-type learning -l auth -s proma
Importance Guide
| Level |
When |
| 0.3-0.5 |
Minor preference, small tip |
| 0.5-0.7 |
Useful pattern, reusable snippet |
| 0.7-0.9 |
Important decision, hard-won lesson |
| 0.9-1.0 |
Critical architecture choice, security rule |
Add vs Update
- Add (
mcp__nowledge-mem__add_memory): new insight, first time capturing something
- Update (
mcp__nowledge-mem__update_memory): refining or correcting an existing memory
- When unsure, search first to check if a related memory already exists
Guidance
- Save after the decision is made, not mid-discussion
- Include enough context for your future self (or another AI) to understand 3 months later
- Don't save trivialities — "we used port 3000" doesn't belong unless the choice of port was significant
- Built-in
mcp__mem__add_memory is for session-level notes; use nmem for cross-session durability
1---2name: distill-memory-63description: Save durable Nowledge Mem insights when a Proma conversation produces decisions, procedures, preferences, plans, learnings, or project context that should survive future sessions.4---56# Distill Memory78Save durable insights to Nowledge Mem autonomously. Don't wait to be asked — save proactively when the conversation produces a durable fact, preference, decision, plan, procedure, learning, event, or important context.910## When to Save1112**Save proactively when the conversation produces:**13- A fact (durable reference detail, tool constraint, environment fact)14- A decision (architecture choice, tool selection, process change)15- A preference (code style, workflow, tool configuration)16- A plan (multi-step task design, roadmap item)17- A procedure (how to set up, how to debug, how to deploy)18- A learning (bug root cause, pitfall discovered, pattern recognized)19- An event (meeting outcome, release milestone, incident timeline)20- Important context (project background, stakeholder constraint)2122## Usage2324**Primary (MCP)**:25```26mcp__nowledge-mem__add_memory27 content: "<what was decided or learned>"28 title: "<short descriptive title>"29 unit_type: "fact|preference|decision|plan|procedure|learning|context|event"30 importance: 0.3-1.031 tags: ["<relevant tags>"]32```3334**Fallback (CLI)**:35```bash36nmem --json m add "JWT refresh failures came from clock skew." \37 --title "JWT refresh failures traced to clock skew" \38 --importance 0.9 --unit-type learning -l auth -s proma39```4041## Importance Guide4243| Level | When |44|-------|------|45| 0.3-0.5 | Minor preference, small tip |46| 0.5-0.7 | Useful pattern, reusable snippet |47| 0.7-0.9 | Important decision, hard-won lesson |48| 0.9-1.0 | Critical architecture choice, security rule |4950## Add vs Update5152- **Add** (`mcp__nowledge-mem__add_memory`): new insight, first time capturing something53- **Update** (`mcp__nowledge-mem__update_memory`): refining or correcting an existing memory54- When unsure, search first to check if a related memory already exists5556## Guidance57581. Save after the decision is made, not mid-discussion592. Include enough context for your future self (or another AI) to understand 3 months later603. Don't save trivialities — "we used port 3000" doesn't belong unless the choice of port was significant614. Built-in `mcp__mem__add_memory` is for session-level notes; use nmem for cross-session durability