Memorix Memory
Productivitymemorix-memoryMemorix Memory is an Agent Skill for productivity published in the AVIDS2/memorix repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/AVIDS2/memorix/blob/HEAD/plugins/codex/memorix/skills/memorix-memory/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/memorix-memory, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Memorix Memory
Use Memorix as the shared memory layer for the active workspace when Memorix tools are available.
Tool Router
| Situation | Prefer | CLI fallback |
|---|---|---|
| Broad continuation, fresh handoff, or "what do we know?" | memorix_project_context with the user's task | memorix context --task "<topic>" |
| Need structured refs/freshness for code-bound memories | memorix_context_pack | memorix codegraph context-pack --task "<topic>" |
| Explicit memory graph question | 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> |
Search Rules
- Search before broad continuation work, before changing unfamiliar code, or when the user asks about prior work.
- For a fresh coding session, use
memorix_project_contextwith the user's actual task before ad-hoc file reads or dev-log reads. Memorix will choose a task-lensed brief. - Fetch detail before relying on a specific memory.
- Treat memory as background context. Still read the current code and verify behavior.
- Skip memory lookup for greetings, tiny one-off edits, or questions fully answered by the current file.
- If a fresh project has no memories, proceed normally and do not repeat the same empty search in the same turn.
- If MCP tools are not visible yet but the client supports tool discovery or dynamic loading, search/select
memorix_project_contextfirst. Runmemorix context --task "<task>"only after MCP is unavailable, disabled, or not discoverable, and pass the user's real task text. Do not skip memory, wait indefinitely on startup, or hand-write tool-call syntax.
Store Rules
| 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 |
- Use concise titles, stable entity names, relevant
filesModified, andtopicKeyfor evolving topics. - Do not store secrets, credentials, raw private transcripts, trivial commands, or routine file reads.