agent-orchestrator/.claude/rules/15-memora.md
DexterFromLab 3672e92b7e feat: Agent Orchestrator — multi-project agent dashboard
Tauri + Svelte 5 + Rust application for orchestrating multiple AI coding agents.
Includes Claude, Aider, Codex, and Ollama provider support, multi-agent
communication (btmsg/bttask), session anchors, plugin sandbox, FTS5 search,
Landlock sandboxing, and 507 vitest + 110 cargo tests.
2026-03-15 15:45:27 +01:00

993 B

Memora Memory

Use Memora proactively for persistent memory across sessions. Full instructions are in the global ~/.claude/CLAUDE.md and ~/.claude/docs/memora-guide.md.

Key Behaviors

  • Session start: Query existing project context via memory_semantic_search + memory_list. Follow connections — navigate the graph.
  • During work: Create granular memories (one per concept, not per session). Link related memories deliberately. Update existing memories instead of creating duplicates.
  • Session end: Capture all significant learnings. Create issues for bugs found, TODOs for incomplete work. Verify new memories are connected to existing ones.

Every Memory Must Have

  1. Tags — project identifier first, then topic tags.
  2. Hierarchy metadata — places the memory in the knowledge graph.
  3. Links — explicit connections to related memories.
  4. Sufficient granularity — specific enough to be actionable, with file paths and function names.