/memory-protocol

Persistent memory discipline for Engram contributors. Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.

gentleman-programming@gentleman-programming

GitHub

From plugin

gentleman-programming-engram

5.9k22 skills1 MCP

Install

$ npx -y skills add Gentleman-Programming/engram --skill memory-protocol --agent claude-code

How 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.
You can call itInvoke it directly when you want it.
Slash command/memory-protocol

Context preview

The summary Claude sees to decide when to auto-load this skill.

Persistent memory discipline for Engram contributors. Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.

SKILL.md

memory-protocol.SKILL.md

name: engram-memory-protocol
description: >
  Persistent memory discipline for Engram contributors.
  Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.
license: Apache-2.0
metadata:
  author: gentleman-programming
  version: "1.0"

When to Use

Use this skill when:

Making architecture or implementation decisions
Fixing bugs with non-obvious root causes
Discovering patterns, gotchas, or user preferences
Closing a session or after compaction

---

Save Rules

Call `mem_save` immediately after:

decision
bugfix
pattern/discovery
config/preference changes

Use structured content:

What
Why
Where
Learned

Use stable `topic_key` for evolving topics.

---

Search Rules

On recall requests: `mem_context` first, then `mem_search`.
Before similar work: run proactive `mem_search`.
On first message: if user references the project, a feature, or a problem, call `mem_search` with their keywords before responding.

---