summon-daem0nlisted

# Summoning the Daem0n This skill guides Claude through setting up Daem0n-MCP for various project structures. ## Single Repo Setup For a single repository: ```bash # Daem0n auto-initializes on first get_briefing() # Just ensure you're in the project root ``` ## Multi-Repo Setup (Client/Server Split) When you have related repos that should share context: ### Option A: Consolidated Parent (Recommended) Best when repos are siblings under a common parent: ``` /repos/ ├── backend/ └── client/ ``` **Steps:** 1. **Navigate to parent directory** ```bash cd /repos ``` 2. **Initialize Daem0n in parent** ``` Call get_briefing(project_path="/repos") ``` 3. **If child repos already have .daem0nmcp data, consolidate:** ``` # Link the children first Call link_projects(linked_path="/repos/backend", relationship="same-project") Call link_projects(linked_path="/repos/client", relationship="same-project") # Merge their databases into parent Call consolidate_linked_databases(archive_sources=True) ``` 4. **Verify consolidation** ``` Call get_briefing(project_path="/repos") # Should show combined memory count ``` ### Option B: Linked but Separate Best when repos need their own isolated histories but cross-awareness: ``` # In each repo, link to siblings cd /repos/backend Call link_projects(linked_path="/repos/client", relationship="same-project") cd /repos/client Call link_projects(linked_path="/repos/backend", relationship="same