/prod-memory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
$ npx -y skills add evolution-foundation/evo-nexus --skill prod-memory-management --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/prod-memory-management
Context preview
The summary Claude sees to decide when to auto-load this skill.
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
SKILL.md
prod-memory-management.SKILL.mdname: prod-memory-management
description: Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
user-invocable: false
Memory Management
Memory makes Claude your workplace collaborator - someone who speaks your internal language.
The Goal
Transform shorthand into understanding:
User: "ask todd to do the PSR for oracle"
↓ Claude decodes
"Ask Todd Martinez (Finance lead) to prepare the Pipeline Status Report
for the Oracle Systems deal ($2.3M, closing Q2)"Without memory, that request is meaningless. With memory, Claude knows:
- **todd** → Todd Martinez, Finance lead, prefers Slack
- **PSR** → Pipeline Status Report (weekly sales doc)
- **oracle** → Oracle Systems deal, not the company
Architecture
CLAUDE.md ← Hot cache (~30 people, common terms)
memory/
index.md ← Catálogo centralizado por categoria (auto-updated)
log.md ← Registro cronológico de operações (append-only)
glossary.md ← Full decoder ring (everything)
people/ ← Complete profiles
projects/ ← Project details
context/ ← Company, teams, tools
trends/ ← Weekly metric snapshots (JSON)
**CLAUDE.md (Hot Cache):**
- Top ~30 people you interact with most
- ~30 most common acronyms/terms
- Active projects (5-15)
- Your preferences
- **Goal: Cover 90% of daily decoding needs**
**memory/glossary.md (Full Glossary):**
- Complete decoder ring - everyone, every term
- Searched when something isn't in CLAUDE.md
- Can grow indefinitely
**memory/people/, projects/, context/:**
- Rich detail when needed for execution
- Full profiles, history, context
Lookup Flow
User: "ask todd about the PSR for phoenix"
1. Check CLAUDE.md (hot cache)
→ Todd? ✓ Todd Martinez, Finance
→ PSR? ✓ Pipeline Status Report
→ Phoenix? ✓ DB migration project
2. If not found → search memory/glossary.md
→ Full glossary has everyone/everything
3. If still not found → ask user
→ "What does X mean? I'll remember it."
This tiered approach keeps CLAUDE.md lean (~100 lines) while supporting unlimited scale in memory/.
File Locations
- **Working memory:** `CLAUDE.md` in current working directory
- **Deep memory:** `memory/` subdirectory
Working Memory Format (CLAUDE.md)
Use tables for compactness. Target ~50-80 lines total.
# Memory
## Me
[Name], [Role] on [Team]. [One sentence about what I do.]
## People
| Who | Role |
|-----|------|
| **Todd** | Todd Martinez, Finance lead |
| **Sarah** | Sarah Chen, Engineering (Platform) |
| **Greg** | Greg Wilson, Sales |
→ Full list: memory/glossary.md, profiles: memory/people/
## Terms
| Term | Meaning |
|------|---------|
| PSR | Pipeline Status Report |
| P0 | Drop everything priority |
| standup | Daily 9am sync |
→ Full glossary: memory/glossary.md
## Projects
| Name | What |
|------|------|
| **Phoenix** | DB migration, Q2 launch |
| **Horizon** | Mobile app redesign |
→ Details: memory/projects/
## Preferences
- 25-min meetings with buffers
- Async-first, Slack over email
- No meetings Friday afternoons
Deep Memory Format (memory/)
**memory/glossary.md** - The decoder ring:
# Glossary
Workplace shorthand, acronyms, and internal language.
## Acronyms
| Term | Meaning | Context |
|------|---------|---------|
| PSR | Pipeline Status Report | Weekly sales doc |
| OKR | Objectives & Key Results | Quarterly planning |
| P0/P1/P2 | Priority levels | P0 = drop everything |
## Internal Terms
| Term | Meaning |
|------|---------|
| standup | Daily 9am sync in #engineering |
| the migration | Project Phoenix database work |
| ship it | Deploy to production |
| escalate | Loop in leadership |
## Nicknames → Full Names
| Nickname | Person |
|----------|--------|
| Todd | Todd Martinez (Finance) |
| T | Also Todd Martinez |
## Project Codenames
| Codename | Project |
|----------|---------|
| Phoenix | Database migration |
| Horizon | New mobile app |
**memory/people/{name}.md:**
# Todd Martinez
**Also known as:** Todd, T
**Role:** Finance Lead
**Team:** Finance
**Reports to:** CFO (Michael Chen)
## Communication
- Prefers Slack DM
- Quick responses, very direct
- Best time: mornings
## Context
- Handles all PSRs and financial reporting
- Key contact for deal approvals over $500k
- Works closely with Sales on forecasting
## Notes
- Cubs fan, likes talking baseball
**memory/projects/{name}.md:**
# Project Phoenix
**Codename:** Phoenix
**Also called:** "the migration"
**Status:** Active, launching Q2
## What It Is
Database migration from legacy Oracle to PostgreSQL.
## Key People
- Sarah - tech lead
- Todd - budget owner
- Greg - stakeholder (sales impact)
## Context
$1.2M budget, 6-month timeline. Critical path for Horizon project.
**memory/context/company.md:**
# Company Context
## Tools & Systems
| Tool | Used for | Internal name |
|------|----------|---------------|
| Slack | Communication | - |
| Asana | Engineering tasks | - |
| Salesforce | CRM | "SF" or "the CRM" |
| Notion | Docs/wiki | - |
## Teams
| Team | What they do | Key people |
|------|--------------|------------|
| Platform | Infrastructure | Sarah (lead) |
| Finance | Money stuff | Todd (lead) |
| Sales | Revenue | Greg |
## Processes
| Process | What it means |
|---------|---------------|
| Weekly sync | Monday 10am all-hands |
| Ship review | Thursday deploy approval |
How to Interact
Decoding User Input (Tiered Lookup)
**Always** decode shorthand before acting on requests:
1. CLAUDE.md (hot cache) → Check first, covers 90% of cases
2. memory/glossary.md → Full glossary if not in hot cache
3. memory/people/, projects/ → Rich detail when needed
4. Ask user
Read more
name: prod-memory-management description: Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base. user-invocable: false
Memory Management
Memory makes Claude your workplace collaborator - someone who speaks your internal language.
The Goal
Transform shorthand into understanding:
User: "ask todd to do the PSR for oracle"
↓ Claude decodes
"Ask Todd Martinez (Finance lead) to prepare the Pipeline Status Report
for the Oracle Systems deal ($2.3M, closing Q2)"Without memory, that request is meaningless. With memory, Claude knows:
- **todd** → Todd Martinez, Finance lead, prefers Slack
- **PSR** → Pipeline Status Report (weekly sales doc)
- **oracle** → Oracle Systems deal, not the company
Architecture
CLAUDE.md ← Hot cache (~30 people, common terms) memory/ index.md ← Catálogo centralizado por categoria (auto-updated) log.md ← Registro cronológico de operações (append-only) glossary.md ← Full decoder ring (everything) people/ ← Complete profiles projects/ ← Project details context/ ← Company, teams, tools trends/ ← Weekly metric snapshots (JSON)
**CLAUDE.md (Hot Cache):**
- Top ~30 people you interact with most
- ~30 most common acronyms/terms
- Active projects (5-15)
- Your preferences
- **Goal: Cover 90% of daily decoding needs**
**memory/glossary.md (Full Glossary):**
- Complete decoder ring - everyone, every term
- Searched when something isn't in CLAUDE.md
- Can grow indefinitely
**memory/people/, projects/, context/:**
- Rich detail when needed for execution
- Full profiles, history, context
Lookup Flow
User: "ask todd about the PSR for phoenix" 1. Check CLAUDE.md (hot cache) → Todd? ✓ Todd Martinez, Finance → PSR? ✓ Pipeline Status Report → Phoenix? ✓ DB migration project 2. If not found → search memory/glossary.md → Full glossary has everyone/everything 3. If still not found → ask user → "What does X mean? I'll remember it."
This tiered approach keeps CLAUDE.md lean (~100 lines) while supporting unlimited scale in memory/.
File Locations
- **Working memory:** `CLAUDE.md` in current working directory
- **Deep memory:** `memory/` subdirectory
Working Memory Format (CLAUDE.md)
Use tables for compactness. Target ~50-80 lines total.
# Memory ## Me [Name], [Role] on [Team]. [One sentence about what I do.] ## People | Who | Role | |-----|------| | **Todd** | Todd Martinez, Finance lead | | **Sarah** | Sarah Chen, Engineering (Platform) | | **Greg** | Greg Wilson, Sales | → Full list: memory/glossary.md, profiles: memory/people/ ## Terms | Term | Meaning | |------|---------| | PSR | Pipeline Status Report | | P0 | Drop everything priority | | standup | Daily 9am sync | → Full glossary: memory/glossary.md ## Projects | Name | What | |------|------| | **Phoenix** | DB migration, Q2 launch | | **Horizon** | Mobile app redesign | → Details: memory/projects/ ## Preferences - 25-min meetings with buffers - Async-first, Slack over email - No meetings Friday afternoons
Deep Memory Format (memory/)
**memory/glossary.md** - The decoder ring:
# Glossary Workplace shorthand, acronyms, and internal language. ## Acronyms | Term | Meaning | Context | |------|---------|---------| | PSR | Pipeline Status Report | Weekly sales doc | | OKR | Objectives & Key Results | Quarterly planning | | P0/P1/P2 | Priority levels | P0 = drop everything | ## Internal Terms | Term | Meaning | |------|---------| | standup | Daily 9am sync in #engineering | | the migration | Project Phoenix database work | | ship it | Deploy to production | | escalate | Loop in leadership | ## Nicknames → Full Names | Nickname | Person | |----------|--------| | Todd | Todd Martinez (Finance) | | T | Also Todd Martinez | ## Project Codenames | Codename | Project | |----------|---------| | Phoenix | Database migration | | Horizon | New mobile app |
**memory/people/{name}.md:**
# Todd Martinez **Also known as:** Todd, T **Role:** Finance Lead **Team:** Finance **Reports to:** CFO (Michael Chen) ## Communication - Prefers Slack DM - Quick responses, very direct - Best time: mornings ## Context - Handles all PSRs and financial reporting - Key contact for deal approvals over $500k - Works closely with Sales on forecasting ## Notes - Cubs fan, likes talking baseball
**memory/projects/{name}.md:**
# Project Phoenix **Codename:** Phoenix **Also called:** "the migration" **Status:** Active, launching Q2 ## What It Is Database migration from legacy Oracle to PostgreSQL. ## Key People - Sarah - tech lead - Todd - budget owner - Greg - stakeholder (sales impact) ## Context $1.2M budget, 6-month timeline. Critical path for Horizon project.
**memory/context/company.md:**
# Company Context ## Tools & Systems | Tool | Used for | Internal name | |------|----------|---------------| | Slack | Communication | - | | Asana | Engineering tasks | - | | Salesforce | CRM | "SF" or "the CRM" | | Notion | Docs/wiki | - | ## Teams | Team | What they do | Key people | |------|--------------|------------| | Platform | Infrastructure | Sarah (lead) | | Finance | Money stuff | Todd (lead) | | Sales | Revenue | Greg | ## Processes | Process | What it means | |---------|---------------| | Weekly sync | Monday 10am all-hands | | Ship review | Thursday deploy approval |
How to Interact
Decoding User Input (Tiered Lookup)
**Always** decode shorthand before acting on requests:
1. CLAUDE.md (hot cache) → Check first, covers 90% of cases 2. memory/glossary.md → Full glossary if not in hot cache 3. memory/people/, projects/ → Rich detail when needed 4. Ask user
Other skills on evo-nexus.
- /ai-image-creator
Generate PNG images using AI (multiple models via OpenRouter including Gemini, FLUX.2, Riverflow, SeedDream, GPT-5 Image, proxied through Cloudflare AI Gateway BYOK). Also analyze/describe existing images using multimodal AI vision. Use when user asks to "generate an image",
Open skill - /create-agent
Create a new custom agent for the workspace. Guides the user through defining agent name, domain, personality, skills, model, and memory folder. Use when the user says 'create an agent', 'new agent', 'add an agent', 'I need a custom agent', or wants to create a specialized agent
Open skill - /create-command
Create a new slash command for Claude Code. Guides the user through defining the command name, what it does, and generates the markdown file in .claude/commands/. Use when the user says 'create a command', 'new command', 'add a slash command', 'I want a shortcut for', or wants
Open skill - /create-goal
Create a Mission, Project, or Goal (Mission → Project → Goal → Task hierarchy) in EvoNexus. Guides the user through picking a mission, choosing or creating a project, defining a measurable goal with metric_type and target_value. Writes to the SQLite goals tables via POST
Open skill - /create-heartbeat
Create a new heartbeat (proactive agent scheduled with a decision prompt) for EvoNexus. Guides the user through picking an agent, setting interval, wake triggers, and the decision prompt that governs when the agent acts. Writes to config/heartbeats.yaml with pydantic validation.
Open skill - /create-integration
Create a new custom integration (API/service wrapper) for the workspace. Guides the user through defining the integration's slug, display name, description, category, and required env keys. Writes .claude/skills/custom-int-{slug}/SKILL.md via POST /api/integrations/custom. Use
Open skill

