Stats
Actions
Tags
From mddesign
Save or recall via the three-tier memory layer. Routes to scratch (file-tier), WHERE (QMD via code-memory-router), or WHY (MemPalace via code-memory-router). Every WHY-tier write goes through the HITL gate.
How this command is triggered — by the user, by Claude, or both
Slash command
/mddesign:memory save [--tier scratch|where|why] <text> | recall <query>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /mddesign:memory Three-tier memory operations. ## Save ### `/mddesign:memory save <text>` (default tier: scratch) Appends to `.agents/memory/scratch/<topic>.md` where `<topic>` is the active phase id from `task_plan.md`, or `general` if no plan. Fast, low-stakes, session-scoped. ### `/mddesign:memory save --tier why <text>` Proposes a promotion to MemPalace WHY tier. HITL gate before write. On approval, invokes `/memory-router` with MemPalace save pattern. ### `/mddesign:memory save --tier where <text>` WHERE is populated by QMD automatically when it indexes project markdown. Explici...
Three-tier memory operations.
/mddesign:memory save <text> (default tier: scratch)Appends to .agents/memory/scratch/<topic>.md where <topic> is the active phase id from task_plan.md, or general if no plan. Fast, low-stakes, session-scoped.
/mddesign:memory save --tier why <text>Proposes a promotion to MemPalace WHY tier. HITL gate before write. On approval, invokes /memory-router with MemPalace save pattern.
/mddesign:memory save --tier where <text>WHERE is populated by QMD automatically when it indexes project markdown. Explicit write is rarely needed; this sub-command exists for completeness and is rate-limited to one-line annotations.
/mddesign:memory recall <query>Routes based on query prefix:
/memory-router/memory-routerAlways prints the source tier next to each result.
task_plan.md, findings.md, or progress.md..agents/memory/scratch/. Never elsewhere.See skills/memory-layer/SKILL.md for full routing logic and conventions.
npx claudepluginhub othmanadi/mddesign --plugin mddesign/memorySaves valuable session insights — decisions, patterns, gotchas — to a daily markdown file in `.claude/storage/`. Accepts optional context string.
/memoryPerforms read-side memory operations on knowledge graph: search past decisions, load session context, view history, visualize. Supports subcommands like search, load, history, viz, status.
/memoryManages project memory using MEMORY.md index and modular .oma/rules packages. Audits index health and topic coverage, lists active rules by task/paths, and plans updates.
/memorySaves important content to a long-term memory database. Accepts explicit content, follows instructions to extract from context, or auto-summarizes session highlights.
/memoryManages persistent project memory-bank files (progress.md, architecture.md) for cross-session continuity. Supports load (restore context), status (show state), sync (update files).
/memoryManages encrypted memory entries for sensitive data like credentials, API keys, and notes. Supports add, search, list, show, delete with optional AES-256 via SQLCipher.