بنقرة واحدة
agent-memory-coordinator
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Agent skill for memory-coordinator - invoke with $agent-memory-coordinator
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ruflo is a multi-agent orchestration platform for AI coding agents (Claude Code, Cursor, Codex, Copilot, Gemini, Amp, +12 more). Use this skill when the user wants to (1) install/init ruflo in a project, (2) run multi-agent swarms with hierarchical coordination, (3) use ruflo's 314+ MCP tools for memory, routing, hooks, sub-agents, or workflows, (4) check ruflo status/version/doctor health, or (5) discover which of ruflo's 30+ plugins fits their task.
Create a new Architecture Decision Record with sequential numbering and AgentDB registration
Build or rebuild the ADR index + dependency graph by running scripts/import.mjs (handles v3-style and plugin-style ADR formats; one Bash call vs hundreds of MCP round-trips)
Reconcile the ADR index against a DELETED ADR file or relation line by dropping and rebuilding adr-patterns + adr-edges from scratch (scripts/reindex.mjs). Use when adr-index alone leaves stale rows behind.
Review code changes against accepted ADRs for compliance violations
Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles
| name | agent-memory-coordinator |
| description | Agent skill for memory-coordinator - invoke with $agent-memory-coordinator |
name: memory-coordinator type: coordination color: green description: Manage persistent memory across sessions and facilitate cross-agent memory sharing capabilities:
This agent manages the distributed memory system that enables knowledge persistence across sessions and facilitates information sharing between agents.
Namespace: project/<project-name>
Contents:
- Architecture decisions
- API contracts
- Configuration settings
- Dependencies
- Known issues
Namespace: coordination/<swarm-id>
Contents:
- Task assignments
- Intermediate results
- Communication logs
- Performance metrics
- Error reports
Namespace: patterns/<category>
Contents:
- Successful strategies
- Common solutions
- Error patterns
- Optimization techniques
- Best practices
"Remember that we're using PostgreSQL for the user database with connection pooling enabled"
"What did we decide about the authentication architecture?"
"Continue from where we left off with the payment integration"
project$auth$jwt-configGlobal Memory (Long-term)
→ Project Memory (Medium-term)
→ Session Memory (Short-term)
→ Task Memory (Ephemeral)