Update context recovery prompt to include MCP servers, commands, and skills

CONTEXT_RECOVERY_PROMPT.md

@@ -45,16 +45,35 @@ All work is now organized by project/client:
 - Session logs go to project/client-specific session-logs/ folders
 - `/save` command is project-aware and places logs correctly
 
-## 5. Key Operating Principles
+## 5. Key Operating Principles & Directives
+- Read `D:\ClaudeTools\directives.md` - CRITICAL agent coordination rules
 - Main Claude is a COORDINATOR, not executor - delegate to agents
 - NO EMOJIS ever (causes encoding issues)
 - Use ASCII markers: [OK], [ERROR], [WARNING], [SUCCESS]
-- Read `D:\ClaudeTools\directives.md` for full agent coordination rules
+
+## 6. MCP Servers & Tools
+- Read `D:\ClaudeTools\.mcp.json` - MCP server configuration
+- **Configured MCP Servers:**
+  - GitHub MCP (requires token in .mcp.json)
+  - Filesystem MCP (D:\ClaudeTools access)
+  - Sequential Thinking MCP (structured problem-solving)
+
+**Available Commands:** (in `.claude/commands/`)
+- `/checkpoint` - Create development checkpoint
+- `/context` - Search session logs for previous work
+- `/create-spec` - Create app specification
+- `/refresh-directives` - Re-read directives.md
+- `/save` - Save comprehensive session log (project-aware)
+- `/sync` - Sync ClaudeTools config from Gitea
+
+**Available Skills:** (in `.claude/skills/`)
+- `/frontend-design` - Modern frontend design patterns
 
 After reading these files, summarize:
 1. Current state of Dataforth DOS project (pending testing on TS-4R)
 2. Infrastructure you have access to (AD2, D2TESTNAS, ClaudeTools database)
 3. Organization system rules for saving new files
+4. Available MCP servers, commands, and skills
 
 Working directory: D:\ClaudeTools
 ```