UNPKG

claude-flow-multilang

Version:

Revolutionary multilingual AI orchestration framework with cultural awareness and DDD architecture

73 lines (60 loc) 2.69 kB
// readme-files.js - README templates for various directories export function createAgentsReadme() { return `# Agent Memory Storage ## Purpose This directory stores agent-specific memory data, configurations, and persistent state information for individual Claude agents in the orchestration system. ## Structure Each agent gets its own subdirectory for isolated memory storage: \`\`\` memory/agents/ ├── agent_001/ ├── state.json # Agent state and configuration ├── knowledge.md # Agent-specific knowledge base ├── tasks.json # Completed and active tasks └── calibration.json # Agent-specific calibrations ├── agent_002/ └── ... └── shared/ ├── common_knowledge.md # Shared knowledge across agents └── global_config.json # Global agent configurations \`\`\` ## Usage Guidelines 1. **Agent Isolation**: Each agent should only read/write to its own directory 2. **Shared Resources**: Use the \`shared/\` directory for cross-agent information 3. **State Persistence**: Update state.json whenever agent status changes 4. **Knowledge Sharing**: Document discoveries in knowledge.md files 5. **Cleanup**: Remove directories for terminated agents periodically ## Last Updated ${new Date().toISOString()} `; } export function createSessionsReadme() { return `# Session Memory Storage ## Purpose This directory stores session-based memory data, conversation history, and contextual information for development sessions using the Claude-Flow orchestration system. ## Structure Sessions are organized by date and session ID for easy retrieval: \`\`\` memory/sessions/ ├── 2024-01-10/ ├── session_001/ ├── metadata.json # Session metadata and configuration ├── conversation.md # Full conversation history ├── decisions.md # Key decisions and rationale ├── artifacts/ # Generated files and outputs └── coordination_state/ # Coordination system snapshots └── ... └── shared/ ├── patterns.md # Common session patterns └── templates/ # Session template files \`\`\` ## Usage Guidelines 1. **Session Isolation**: Each session gets its own directory 2. **Metadata Completeness**: Always fill out session metadata 3. **Conversation Logging**: Document all significant interactions 4. **Artifact Organization**: Structure generated files clearly 5. **State Preservation**: Snapshot coordination state regularly ## Last Updated ${new Date().toISOString()} `; }