CLAUDE.md serves as a hot cache of ~30 frequent contacts, common terms, and active projects; memory/ directory stores the complete glossary, detailed profiles, and project context
Tiered lookup flow checks CLAUDE.md first (covers 90% of daily decoding), then searches memory/glossary.md, then asks the user for unknown terms
Fetches memory-management from anthropics/knowledge-work-plugins and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/memory-management
Restart Cursor to activate memory-management. Access via /memory-management in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
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/
glossary.md ← Full decoder ring (everything)
people/ ← Complete profiles
projects/ ← Project details
context/ ← Company, teams, tools
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:
# GlossaryWorkplace 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 IsDatabase 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
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
