daem0nmcp-protocollisted

# The Daem0n's Protocol ## Overview When Daem0nMCP memory tools are available, you MUST follow this protocol. Memory without discipline is noise. **Core principle:** Check before you change, record what you decide, track whether it worked. ## Tool Detection First, verify Daem0nMCP tools are available: ``` Look for these tools in your available tools: - mcp__daem0nmcp__get_briefing - mcp__daem0nmcp__context_check - mcp__daem0nmcp__remember - mcp__daem0nmcp__record_outcome - mcp__daem0nmcp__link_memories - mcp__daem0nmcp__trace_chain - mcp__daem0nmcp__get_graph - mcp__daem0nmcp__find_code - mcp__daem0nmcp__analyze_impact - mcp__daem0nmcp__index_project ``` **If tools are NOT available:** This skill does not apply. Proceed normally. **If tools ARE available:** Follow the protocol below. No exceptions. ## The Protocol ### 1. SESSION START (Non-Negotiable) ``` IMMEDIATELY when you have daem0nmcp tools: mcp__daem0nmcp__get_briefing() DO NOT: - Ask user what they want first - Skip briefing because "it's a quick task" - Assume you remember from last session ``` The briefing loads: - Past decisions and their outcomes - Warnings and failed approaches to AVOID - Patterns to FOLLOW - Git changes since last session ### 2. BEFORE ANY CODE CHANGES ``` BEFORE touching any file: mcp__daem0nmcp__context_check(description="what you're about to do") OR for specific files: mcp__daem0nmcp__recall_for_file(file_path="path/to/file") ``` **If context_check returns:** - **WARNING:*