Memory sync
Skill a-ariff/ariff-claude-plugins/plugins/memory-sync/skills/memory-sync
65 plugins that turn Claude Code into an autonomous development team. 24 agents, 34 skills, 5 hooks. Includes 12-plugin anti-hallucination suite. One-line install.
npx -y skills add a-ariff/ariff-claude-plugins --skill memory-syncAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Memory Sync Skill
SKILL.md
2.0 KB, as published. Nobody here has run it
Memory Sync Skill
How to manually sync learnings to memory systems after tasks.
Dual Memory Architecture
Ariff uses two complementary memory systems:
- mem0-memory-mcp - AI-native semantic memory for quick recall
- obsidian-memory - Structured vault for long-term knowledge
Manual Sync Commands
Quick Save to mem0
Use mcp__mem0-memory-mcp__add_memory to store:
- Task context and solution
- Key learnings and gotchas
- Useful commands discovered
Save to Obsidian
Use mcp__obsidian-memory__create_note with:
- path: "tasks/YYYY-MM-DD-task-slug.md"
- content: Structured task notes
Memory Entry Template
## Task: [Brief Title]
Date: [YYYY-MM-DD]
Device: [hostname]
### Problem
[What was the issue/request]
### Solution
[How it was resolved]
### Key Learnings
- [Learning 1]
- [Learning 2]
### Related
- Previous tasks: [links]
- Documentation: [links]
Creating Agent Instructions
When a mistake or pattern should be avoided in future:
-
Create instruction file at:
Ariff-code-config/instructions/[category]-[topic].instructions.md -
Use format:
--- description: [What this instruction prevents/ensures] applyTo: [glob pattern like **/*.py or **/canvas/**] --- # [Rule Title] ## Context [When this applies] ## Rule [What to do/not do] ## Example [Good vs bad example] -
Add to 00_INSTRUCTIONS_INDEX.md if significant
Reconciliation
If memories seem out of sync:
- Query both systems for topic
- Compare entries
- Update older system with newer info
- Remove duplicates with less detail
When to Save
Save memory when:
- ✅ Task completed successfully
- ✅ Discovered non-obvious solution
- ✅ Made mistake worth remembering
- ✅ Found useful tool/command
- ✅ Clarified user preference
Skip saving when:
- ❌ Trivial task (simple file edit)
- ❌ Already documented elsewhere
- ❌ One-off unique situation