メニュー
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | memorix-memory |
| description | Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task. |
Use Memorix as the shared memory layer for the active workspace when Memorix tools are available.
| Situation | Prefer | CLI fallback |
|---|---|---|
| Broad continuation, memory overview, or "what do we know?" | memorix_graph_context | memorix memory graph-context --query "<topic>" |
| Specific past decision, bug, file, or change | memorix_search | memorix memory search --query "<topic>" |
| Need the full source for a search hit | memorix_detail | memorix memory detail --id <id> |
| Need the sequence around one memory | memorix_timeline | memorix memory timeline --id <id> |
| Learned reusable project knowledge | memorix_store | memorix memory store --type <type> --entity <name> --title "<title>" "<text>" |
| Task or bug is complete/outdated | memorix_resolve | memorix memory resolve --ids <ids> |
| What to store | Type |
|---|---|
| Architecture or product decision | decision |
| Bug and fix that may recur | problem-solution |
| Non-obvious pitfall | gotcha |
| How a subsystem works | how-it-works |
| Important implementation change | what-changed |
| Accepted compromise | trade-off |
filesModified, and topicKey for evolving topics.Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether session_start is useful.