A Rust-native agentic memory substrate built on the selene-db graph engine: a bi-temporal knowledge graph, hybrid retrieval, and an optional MCP server.
Skill Claude CodeCodex
Send, poll, wait for, and acknowledge durable addressed agent-to-agent messages in Aionforge Memory (messagesend, messagepoll, messagewait, messageack) and subscribe to room resources. Use to hand a brief to another agent, page a teammate, wait for a reply, coordinate a multi-agent workflow, or drain an inbox …
Skill Claude CodeCodex
One-time setup that lays a foundational Aionforge Memory substrate for a fresh project — resolve identity, seed conventions and architecture decisions as captures, stand up a work-item backlog skeleton, and verify recall. Use when a project's memory is empty or new, or when the user asks to set up, bootstrap…
Skill Claude CodeCodex
Capture durable Aionforge Memory records for decisions, user preferences, project facts, release outcomes, validation results, handoffs, corrections, and reusable failure patterns. Use proactively during substantial work and whenever the user asks to remember or update memory.
Skill Claude CodeCodex
Use Aionforge Memory as the working substrate for a multi-step task. Trigger for implementation, debugging, review, release, planning, incidents, handoffs, or any session where prior context and durable follow-up matter.
Skill Claude CodeCodex
Inspect, consolidate, audit, forget, or restore Aionforge Memory. Use when the user asks about memory health, backlog, provenance, stale records, corrections, deletion, restoration, or why a memory was recalled.
Skill Claude CodeCodex
Search Aionforge Memory before planning, answering, coding, review, debugging, release, or continuation work. Use proactively whenever prior decisions, user preferences, project facts, failures, or handoffs could change the answer.
Skill Claude CodeCodex
Track tasks, blockers, TODOs, plans, and follow-ups as durable Aionforge Memory work items. Use proactively when a multi-step task, backlog, plan, or handoff appears, and whenever the user mentions tasks, status, or what is left to do. Work items are persistent and status-tracked, distinct from decaying memory…