memorix

Store and retrieve engineering memories with Memorix MCP tooling.

Updated Apr 9, 2026

Search Tags:#documentation #codebase #memory #engineering #knowledge-management #memory-store #memorix

Ready to run

npx skills add https://github.com/HuaGCS/Hahobot --skill memorix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: memorix
Source: https://github.com/HuaGCS/Hahobot/tree/main/hahobot/skills/memorix
Command: npx skills add https://github.com/HuaGCS/Hahobot --skill memorix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Memorix stores workspace memories such as design rationale, prior fixes, and reusable engineering knowledge to keep engineering teams aligned and reduce memory loss.

Core Features & Use Cases

Project history and rationale: Capture why decisions were made and how design evolved.
Knowledge reuse: Quickly recall implementation patterns and rationale across tasks.
Cross-team collaboration: Share memories tied to a workspace; ensure continuity after handoffs.

Quick Start

Store a concise engineering rationale for the current task using memorix_store.

Frequently Asked Questions about memorix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I store engineering rationale and design decisions in a shared workspace?▼

Memorix stores engineering rationale in a workspace using memorix_store, capturing design decisions, tradeoffs, and implementation history to anchor team knowledge and prevent context loss across tasks.

What is the best way to retain codebase knowledge after refactoring or team handoffs?▼

Retaining codebase knowledge after refactoring requires storing design rationale and prior fixes in a workspace-scoped memory, ensuring cross-team continuity and reducing memory loss during handoffs.

Can I use memorix to share engineering knowledge across multiple teams?▼

Yes, memorix supports cross-team collaboration by tying engineering memories to an active workspace, enabling shared access to design rationale and implementation history for continuity after handoffs.

Do I need MCP tooling to record implementation history and tradeoffs?▼

Yes, recording implementation history and tradeoffs requires Memorix MCP tooling to enable workspace-scoped storage with safe, verifiable persistence using memorix_store and memorix_store_reasoning functions.

When should I record engineering memories in my codebase workflow?▼

Record engineering memories after refactors, when documenting tradeoffs, or when capturing design rationale, ensuring implementation patterns and decision history remain accessible for future tasks and cross-team knowledge sharing.