OpenLtm

USE WHEN separating trusted instructions from untrusted content or tool output.

USE WHEN hardening command execution, path handling, or installer boundaries.

USE WHEN handling credentials, env vars, logs, tests, or docs safely.

Reference for LTM memory commands, context hooks, and DB schema; use when the user mentions learning, recalling, forgetting, relating, or capturing memory, or when a session starts or the project changes.

Mines LTM memories from past git commits. Use when onboarding a repo into LTM, backfilling history after enabling gitLearn, or harvesting patterns after a sprint.

Reference for retrieved patterns and lessons from past sessions; use when prior fixes, gotchas, decisions, or earlier sessions may apply, or when asked what we learned before.

The LTM memory-tool contract — names, ritual, categories, phase map. USE WHEN recalling, learning, relating, or restoring memory.

Start, stop, or check the LTM graph visualization server; use when the user asks to open, launch, stop, kill, or check graph-server status.

Session context persistence for project goals, decisions, progress, and gotchas; use when restoring project state, managing session notes, or checking whether context was injected at startup.

Explores code + LTM, then writes acceptance criteria. USE WHEN defining what to build before planning.