memorix

name	memorix
description	Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.

Memorix

Memorix is a shared memory layer for the active workspace when Memorix tools are available. Use this root skill as a router, then prefer the focused skill for the task.

Skill Router

Task	Use
Recall/store durable workspace context	memorix-memory
Record or recover why a decision was made	memorix-reasoning
Resume sessions, bind HTTP projects, or prepare handoff	memorix-sessions
Use commit history as evidence	memorix-git-memory
Promote repeated knowledge into reusable guidance	memorix-mini-skills
Coordinate explicit subagent work	memorix-orchestrate
Diagnose MCP/setup/hooks/control-plane issues	memorix-troubleshooting

Default Loop

1. For broad continuation, first call memorix_project_context with the user's actual task so Memorix can choose a task-lensed brief.
2. Search only when more prior context would materially help.
3. Fetch detail before relying on a specific memory.
4. Store decisions, fixes, gotchas, and handoff context that future sessions should not rediscover.
5. Use CLI fallbacks only after MCP tools are confirmed unavailable.

Claude Code can report MCP servers as pending during print-mode startup. That is not a failure by itself. Claude Code supports MCP tool search, and the Memorix Claude plugin asks Claude to eagerly load its small core tool set. In headless/print-mode, if Memorix tools are not in the first visible tool list, search/select memorix_project_context before using shell fallback. Run memorix context --task "<task>" only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text.

Do not store secrets, credentials, raw private transcripts, or trivial one-off actions. Treat memory as context, not as a substitute for reading code and verifying behavior.