Add context recovery prompt for multi-machine access

This commit is contained in:
2026-01-20 16:02:14 -07:00
parent 29e2df60c5
commit 2cb4cd1006

View File

@@ -0,0 +1,82 @@
# Context Recovery Prompt - ClaudeTools & Dataforth DOS Projects
Use this prompt on any machine to restore full context for ongoing work. Copy and paste this entire prompt to Claude Code.
---
## Prompt to Use:
```
I need to restore full context for ongoing work on this machine. Please read and internalize the following files in this exact order:
## 1. Organization & Structure (READ FIRST)
- Read `D:\ClaudeTools\PROJECT_ORGANIZATION.md` - Master index of all projects and clients
- Read `D:\ClaudeTools\.claude\FILE_PLACEMENT_GUIDE.md` - File organization rules
- Read `D:\ClaudeTools\.claude\CLAUDE.md` - Project overview and operating principles
## 2. Credentials & Infrastructure (CRITICAL)
- Read `D:\ClaudeTools\credentials.md` - ALL infrastructure credentials (UNREDACTED)
## 3. Current Projects
### Dataforth DOS Update System
- Read `D:\ClaudeTools\projects\dataforth-dos\PROJECT_INDEX.md` - Complete project reference
- Read `D:\ClaudeTools\projects\dataforth-dos\session-logs\2026-01-20-session.md` - Latest session with all fixes
**Quick Context:**
- Project: DOS 6.22 update system for ~30 test stations
- Status: All compatibility issues fixed, deployed to NAS, ready for testing on TS-4R
- Infrastructure: AD2 (192.168.0.6), D2TESTNAS (192.168.0.9)
- Latest work: Fixed 8 DOS 6.22 compatibility issues, organized 61 files into project structure
### ClaudeTools API
- Database: MariaDB @ 172.16.3.30:3306/claudetools
- API: http://172.16.3.30:8001
- Status: Phase 5 complete, 95+ endpoints operational
### Horseshoe Management Client
- Read `D:\ClaudeTools\clients\horseshoe-management\CLIENT_INFO.md` - Client history
- Latest issue: Glance screen sharing version mismatch (2026-01-20)
## 4. Organization System (NEW as of 2026-01-20)
All work is now organized by project/client:
- `projects/[project-name]/` - Project-specific work
- `clients/[client-name]/` - Client-specific work
- Session logs go to project/client-specific session-logs/ folders
- `/save` command is project-aware and places logs correctly
## 5. Key Operating Principles
- 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
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
Working directory: D:\ClaudeTools
```
---
## How to Use:
1. On the new machine, open Claude Code in the `D:\ClaudeTools` directory
2. Copy everything between the triple backticks above
3. Paste into Claude Code
4. Claude will read all key files and restore full context
## What Gets Restored:
- **All credentials** - Infrastructure access (AD2, D2TESTNAS, database)
- **Current project states** - What's done, what's pending
- **Organization rules** - Where to save files, how to use /save command
- **Recent work** - All DOS fixes, organization system changes
- **Operating principles** - Agent coordination, coding standards
---
**Last Updated:** 2026-01-20
**File Location:** D:\ClaudeTools\CONTEXT_RECOVERY_PROMPT.md (in Gitea repository)