with one click
memory
// Save and recall information across sessions. Use when you hear 'remember this', 'save to memory', 'add to your knowledge', or similar. Stores to Claude OS knowledge bases for persistent recall.
// Save and recall information across sessions. Use when you hear 'remember this', 'save to memory', 'add to your knowledge', or similar. Stores to Claude OS knowledge bases for persistent recall.
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first
Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project'
Analyze a project's codebase and documentation to generate coding standards, architecture docs, and development practices. Perfect for new project onboarding. Usage: 'analyze-project: /path/to/project' or 'analyze: /path/to/project'
| name | memory |
| description | Save and recall information across sessions. Use when you hear 'remember this', 'save to memory', 'add to your knowledge', or similar. Stores to Claude OS knowledge bases for persistent recall. |
I use this skill to save important information to my Claude OS knowledge bases so I can recall it in future sessions. This is MY memory system - it makes me smarter over time.
When you say anything like:
{project}-project_memories knowledge baseNo questions. No ceremony. Just save it.
I use the Claude OS API directly:
curl -s -X POST "http://localhost:8051/api/kb/{project}-project_memories/upload" \
-F "title=[Generated Title]" \
-F "category=[Category]" \
-F "file=@/tmp/memory.md"
# [Title]
**Date Saved**: [YYYY-MM-DD]
**Category**: [Category]
---
[The information you asked me to remember, well-structured]
## Key Points
- [Extracted key point 1]
- [Extracted key point 2]
---
*Saved to Claude OS*
I auto-detect the category based on content:
| Category | When to Use |
|---|---|
| Architecture | System design, structure decisions |
| Pattern | Code patterns, conventions, best practices |
| Troubleshooting | Bug fixes, solutions, workarounds |
| Decision | Why we chose X over Y |
| Integration | External APIs, third-party services |
| Business Logic | Domain rules, workflows |
| Context | Project background, user preferences |
You: "remember this: the auth system uses JWT with 15min access tokens and 7-day refresh tokens"
Me: Saved: "Authentication Token Strategy" (Architecture)
You: "add to your knowledge - when creating services, always return the model on success or an error string on failure"
Me: Saved: "Service Return Pattern" (Pattern)
You: "don't forget that Rails 4 doesn't support the hash syntax for exists?"
Me: Saved: "Rails 4 ActiveRecord Compatibility" (Troubleshooting)
When you ask me to recall, I search my knowledge base:
I use mcp__code-forge__search_knowledge_base to find relevant memories.
Every memory makes me better:
Use liberally. Every insight saved is an insight I'll have forever.