memory-recorder
Memory-Recorder
This skill manages the project's long-term memory, Serena. Its purpose is to prevent indiscriminate data storage and strictly select high-value reusable information for structured recording.
1. Memory Storage Principles
Storage Whitelist (Save)
- System structural information that rarely changes over time (Architecture, Environment configs).
- Confirmed facts that are repeatedly referenced.
- Behaviors verified by official documents or actual tests/logs.
- Finalized conclusions reached after debate (Decision Records).
- Frequently occurring failure patterns and solutions (Troubleshooting Guide).
Storage Blacklist (Do Not Save)
- Simple guesses or unverified hypotheses.
- Uncertain possibilities like "Items might be...".
- Temporary phenomena or issues limited to specific transient situations.
- Subjective judgments or impressions.
- Unverified experiment results.
2. Memory Initialization Template
When initializing memory for a new project or module, use the following template to structure it.
# [Project/Module Name] Context
## Basic Info
- Service Name:
- Runtime Environment:
- Main Language / Framework:
- Communication Protocol:
- Key Infra Components (Proxy, CDN, LB, etc.):
## Architecture Fixed Facts
- Request/Response Flow:
- Streaming / Buffering Characteristics:
- Timeout / Connection Policy:
## Fact Base
- [Source: Log/Test] ...
- [Source: Doc] ...
## Known Patterns
### [Pattern Name]
- Occurrence Condition:
- Solution / Response:
3. Memory Update Rules during Incident Response
Follow these rules when updating memory during an Incident.
- Post-Resolution: Record only after the incident is fully resolved and the cause is solidified. Do not record hypotheses during resolution.
- Field Data First: If existing memory conflicts with new actual field data, prioritize and record the latest field data (overwrite) and specify the change history.
- Clarity: Write concisely so anyone can understand "What was the problem and how was it solved".
4. Usage Method
When the Orchestrator or User requests "Remember this," or when a significant discovery is made, use the write_memory tool to record it.
You must adhere to the principles above to judge the value of the information before writing.
More from first-fluke/mimic
qa-agent
Quality assurance specialist for security, performance, accessibility, and comprehensive testing
1mimic-qa
Perform end-to-end QA testing on the MIMIC extension. Use this skill to verify core functionalities like shell hooking, analysis, synthesis, and sidebar UI.
1pm-agent
Product manager that decomposes requirements into actionable tasks with priorities and dependencies
1product-planner
Act as a 30-year veteran Product Manager & System Analyst specialized in Developer Tools and AI Agents. Use this skill to brainstorm features, define requirements, and create technical specs for MIMIC.
1frontend-agent
Frontend specialist for React, Next.js, TypeScript, and modern UI development
1veteran-dev
Act as a 30-year veteran Software Architect & Engineer specialized in VS Code Extensions, TypeScript, and Systems Programming. Use for architectural decisions, code reviews, and complex debugging.
1