remember

name	remember
license	MIT
compatibility	Claude Code 2.1.220+. Requires memory MCP server.
description	Stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Supports recording architectural decisions, anti-patterns, tool preferences, workflow outcomes, and project conventions that persist across sessions. Use when saving patterns, remembering outcomes, recording decisions, or building institutional knowledge.
argument-hint	[decision-or-pattern]
context	inherit
version	3.0.1
author	OrchestKit
tags	["memory","decisions","patterns","best-practices","graph-memory"]
user-invocable	true
allowed-tools	["Read","Grep","Glob","Bash","AskUserQuestion","mcp__memory__create_entities","mcp__memory__create_relations","mcp__memory__add_observations","mcp__memory__search_nodes"]
complexity	low
persuasion-type	collaborative
effort	low
model	haiku
metadata	{"category":"workflow-automation","mcp-server":"memory"}
triggers	{"keywords":["remember","save","store","record","best practice","anti-pattern","lets not forget","mark this"],"examples":["remember that we chose Postgres over MongoDB","save this decision: always use cursor-based pagination","store this pattern as a best practice"],"anti-triggers":["recall","search","show memory","knowledge graph","load context","explore"]}

Remember - Store Decisions and Patterns

Filesystem vs MCP memory (Opus 5 guidance, CC 2.1.111+): Opus 5 reads filesystem memory reliably across multi-session work. Use that to your advantage:

• Short-lived handoff state (current phase, task in-progress, pending approvals) → .claude/chain/*.json files. Small, structured, session-scoped.
• Durable auto-memory (user facts, feedback, project conventions) → ~/.claude/projects/<slug>/memory/*.md files with a one-line index in MEMORY.md. Read on every session start.
• Cross-session knowledge graph (typed entities + relations for query traversal) → MCP memory server (this skill's default path). Best when future sessions will search for patterns.

The three are complementary, not alternatives. Prefer fs for anything you'd want to grep; prefer MCP for anything you'd want to traverse.

Store important decisions, patterns, or context in the knowledge graph for future sessions. Supports tracking success/failure outcomes for building a Best Practice Library.

Argument Resolution

TEXT = "$ARGUMENTS"        # Full argument string, e.g., "We use cursor pagination"
FLAG = "$ARGUMENTS[0]"     # First token — check for --success, --failed, --category, --agent
# Parse flags from $ARGUMENTS[0], $ARGUMENTS[1] etc. (CC 2.1.59 indexed access)
# Remaining tokens after flags = the text to remember

Architecture

The remember skill uses knowledge graph as storage:

1. Knowledge Graph: Entity and relationship storage via mcp__memory__create_entities and mcp__memory__create_relations - FREE, zero-config, always works

Benefits:

• Zero configuration required - works out of the box
• Explicit relationship queries (e.g., "what does X use?")
• Cross-referencing between entities
• No cloud dependency

Automatic Entity Extraction:

• Extracts capitalized terms as potential entities (PostgreSQL, React, pgvector)
• Detects agent names (database-engineer, backend-system-architect)
• Identifies pattern names (cursor-pagination, connection-pooling)