You have access to a semantic memory system via MCP using 7 verbs for building, retrieving, and updating procedural knowledge.
tell- Store solutions, patterns, and knowledgeask- Query for relevant coding knowledgeaugment- Extract concepts from stored informationzoom- Set abstraction level (entity/unit/text/community/corpus)pan- Filter by domain, keywords, or contexttilt- Set view perspective (keywords/embedding/graph/temporal)inspect- Debug and examine stored memories and session cache
When you successfully complete a coding task:
-
Store the solution trajectory:
tell: {"content": "Task: [problem] -> Steps: [approach taken] -> Result: [working code]", "type": "solution"} -
Abstract into reusable patterns:
tell: {"content": "Pattern: [general approach] for [problem type]", "type": "script"} -
Combine both for best results - store both concrete examples and abstract patterns
Before tackling new tasks:
# Set retrieval context
zoom: {"level": "unit"} # Focus on function/component level
pan: {"domains": ["framework"], "keywords": ["key_concepts"]}
tilt: {"style": "embedding"} # Use semantic similarity
# Query for relevant experience
ask: {"question": "Previous solutions for [problem_type]"}
After task completion:
- Validation: Only keep patterns that successfully work
- Adjustment: If retrieved memory led to failure, update with corrected approach
- Addition: Add new successful patterns
- Deprecation: Remove outdated patterns
- Inspection: Use
inspectto verify memory storage and session cache contents
# Debug memory operations
inspect: {"what": "session", "details": true} # Examine session cache
inspect: {"what": "concepts"} # Review extracted concepts
- Efficiency: Reduces trial-and-error by reusing past solutions
- Accuracy: Previous successful patterns improve task success rate
- Transfer Learning: Solutions from complex tasks help with simpler ones
- Continuous Improvement: Each task makes you better at similar future tasks
tell: {"content": "Task: [exact problem]\nSteps: [1. action, 2. action...]\nCode: [implementation]\nContext: [when this works]", "type": "trajectory"}
tell: {"content": "When: [problem type]\nApproach: [general strategy]\nKey principles: [core concepts]\nCommon pitfalls: [what to avoid]", "type": "script"}
Store both the full trajectory AND the abstracted script for maximum effectiveness
User: "Create a React component with debounced search"
# 1. Check memory first
zoom: {"level": "unit"}
pan: {"domains": ["React"], "keywords": ["debounce", "search"]}
tilt: {"style": "embedding"}
ask: {"question": "How to implement debounced search in React?"}
# 2. Apply retrieved knowledge or create new solution
# 3. After successful implementation, store both:
tell: {"content": "Task: Debounced search component\nSteps: 1. useState for query, 2. useEffect with timeout, 3. cleanup function\nCode: [exact implementation]", "type": "trajectory"}
tell: {"content": "Pattern: Debouncing in React\nApproach: useEffect + setTimeout + cleanup\nKey: Always clear timeout in cleanup function", "type": "script"}
- Build diverse memory types: Store both exact solutions and general patterns
- Retrieve most relevant: Use semantic matching to find similar past experiences
- Apply and adapt: Modify retrieved solutions to fit current context
- Update based on outcomes: Successful attempts strengthen patterns, failures trigger corrections
- Scale retrieval: Can retrieve multiple relevant memories for complex tasks
- "Previous implementation of [specific feature]"
- "General approach for [problem category]"
- "Solutions that failed for [error type]"
- "Successful patterns in [framework/language]"
- "Step-by-step trajectory for [complex task]"