prod-memory-management

Decode workplace shorthand using tiered memory lookups in CLAUDE.md and memory stores.

520|175|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/evolution-foundation/evo-nexus --skill prod-memory-management-evolution-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-memory-management
Source: https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/prod-memory-management
Command: npx skills add https://github.com/evolution-foundation/evo-nexus --skill prod-memory-management-evolution-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of Claude misunderstanding internal workplace shorthand such as nicknames, acronyms, and coded project references, which prevents it from acting like a true collaborator.

Core Features & Use Cases

  • Two-tier memory system: Maintains a hot working cache in CLAUDE.md plus an expandable deep memory store under memory/ for full knowledge coverage.
  • Deterministic lookup flow: Resolves entities and meanings by checking CLAUDE.md first, then memory/glossary.md, then richer profiles and project details as needed.
  • Structured knowledge organization: Uses dedicated directories and files (people/, projects/, context/, trends/, index.md, log.md) to keep decoding consistent and scalable across changing teams and projects.
  • Ongoing memory maintenance guidance: Provides conventions and operations (ingest, query, lint) for keeping hot cache and deep memory synchronized over time.

Quick Start

Tell Claude to “Decode and answer my request using CLAUDE.md first, then memory/ when needed,” and include the shorthand you want resolved (for example, a person nickname and an acronym).

Frequently Asked Questions about prod-memory-management

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

FAQPage Schema
How do I resolve workplace acronyms and project codenames for agent collaboration?

To resolve workplace acronyms and project codenames for agent collaboration, use a tiered lookup approach. Check the hot working cache in CLAUDE.md first, then query deep memory stores like memory/glossary.md and project directories to decode shorthand into accurate context.

How does a two-tier memory system decode internal workplace shorthand?

A two-tier memory system decodes internal workplace shorthand by checking a hot working cache in CLAUDE.md for immediate context, then expanding into deep memory stores under memory/ directories for richer profiles, glossary terms, and project details to ensure accurate entity resolution.

What is the best way to maintain a knowledge base for context decoding across changing teams?

The best way to maintain a knowledge base for context decoding across changing teams is using structured directories for people, projects, and context. Apply index and log conventions to keep the hot cache and deep memory synchronized through ingest, query, and lint operations.

Can I use CLAUDE.md to manage workflow instructions and partial internal language?

Yes, you can use CLAUDE.md to manage workflow instructions and partial internal language. It serves as a hot working cache that accurately resolves ambiguous directives like nicknames and acronyms into the correct people and terms before executing daily collaboration tasks.

Why does my agent misunderstand internal workplace shorthand and nicknames?

Your agent misunderstands internal workplace shorthand and nicknames because it lacks a structured knowledge base for context decoding. Without a tiered lookup flow mapping partial internal language to correct people and projects, reliable task execution fails on ambiguous directives.