Updated frameworks.

docs/changes/framework-updates/HANDOFF-PROMPTS.md

@@ -0,0 +1,160 @@
+# Claude-to-Claude Handoff Prompts
+
+**Purpose**: Ready-to-use prompts for seamless Claude instance transitions during MotoVaultPro modernization.
+
+## 🚀 General Handoff Prompt
+
+```
+I'm continuing MotoVaultPro modernization. Check STATUS.md for current phase and progress. Follow the documented phase files for detailed steps. Use Context7 research already completed. Maintain Modified Feature Capsule architecture and Docker-first development. Update STATUS.md when making progress.
+```
+
+## 📋 Phase-Specific Handoff Prompts
+
+### Phase 1: Analysis & Baseline
+```
+Continue MotoVaultPro Phase 1 (Analysis). Check PHASE-01-Analysis.md for current status. Complete any remaining baseline performance metrics. All Context7 research is done - focus on metrics collection and verification before moving to Phase 2.
+```
+
+### Phase 2: React 19 Foundation  
+```
+Start/continue MotoVaultPro Phase 2 (React 19 Foundation). Check PHASE-02-React19-Foundation.md for detailed steps. Update frontend/package.json dependencies, test compatibility. Use Context7 research already completed for React 19. Maintain Docker-first development.
+```
+
+### Phase 3: React Compiler
+```
+Start/continue MotoVaultPro Phase 3 (React Compiler). Check PHASE-03-React-Compiler.md for steps. Install React Compiler, remove manual memoization, test performance gains. Phase 2 React 19 foundation must be complete first.
+```
+
+### Phase 4: Backend Evaluation
+```
+Start/continue MotoVaultPro Phase 4 (Backend Evaluation). Check PHASE-04-Backend-Evaluation.md. Set up Fastify alongside Express, create feature flags, performance benchmark. Use Context7 Fastify research completed earlier.
+```
+
+### Phase 5: TypeScript Modern
+```
+Start/continue MotoVaultPro Phase 5 (TypeScript Modern). Check PHASE-05-TypeScript-Modern.md. Upgrade TypeScript to 5.4+, update configs, implement modern syntax. Focus on backend and frontend TypeScript improvements.
+```
+
+### Phase 6: Docker Modern
+```
+Start/continue MotoVaultPro Phase 6 (Docker Modern). Check PHASE-06-Docker-Modern.md. Implement multi-stage builds, non-root users, layer optimization. Must maintain Docker-first development philosophy.
+```
+
+### Phase 7: Vehicles Fastify
+```
+Start/continue MotoVaultPro Phase 7 (Vehicles Fastify). Check PHASE-07-Vehicles-Fastify.md. Migrate vehicles feature capsule from Express to Fastify. Maintain Modified Feature Capsule architecture. Test thoroughly before proceeding.
+```
+
+### Phase 8: Backend Complete
+```
+Start/continue MotoVaultPro Phase 8 (Backend Complete). Check PHASE-08-Backend-Complete.md. Migrate remaining features (fuel-logs, stations, maintenance) to Fastify. Remove Express entirely. Update all integrations.
+```
+
+### Phase 9: React 19 Advanced
+```
+Start/continue MotoVaultPro Phase 9 (React 19 Advanced). Check PHASE-09-React19-Advanced.md. Implement Server Components, advanced Suspense, new React 19 hooks. Phase 3 React Compiler must be complete.
+```
+
+### Phase 10: Final Optimization
+```
+Start/continue MotoVaultPro Phase 10 (Final Optimization). Check PHASE-10-Final-Optimization.md. Performance metrics, bundle optimization, production readiness. Compare against baseline metrics from Phase 1.
+```
+
+## 🚨 Emergency Recovery Prompts
+
+### System Failure Recovery
+```
+MotoVaultPro modernization was interrupted. Check STATUS.md immediately for last known state. Check current phase file for exact step. Run verification commands to confirm system state. Check ROLLBACK-PROCEDURES.md if rollback needed.
+```
+
+### Build Failure Recovery
+```
+MotoVaultPro build failed during modernization. Check current phase file for rollback procedures. Run 'make rebuild' in Docker environment. If persistent failure, check ROLLBACK-PROCEDURES.md for phase-specific recovery.
+```
+
+### Dependency Issues
+```
+MotoVaultPro has dependency conflicts during modernization. Check current phase file for expected versions. Use 'npm list' in containers to verify. Rollback package.json changes if needed using git checkout commands in phase files.
+```
+
+## 🔄 Mid-Phase Handoff Prompts
+
+### When Stuck Mid-Phase
+```
+I'm stuck in MotoVaultPro modernization Phase [X]. Check PHASE-[XX]-[Name].md file, look at "Current State" section to see what's completed. Check "Troubleshooting" section for common issues. Update STATUS.md if you resolve the issue.
+```
+
+### Performance Testing Handoff
+```
+Continue MotoVaultPro performance testing. Check current phase file for specific metrics to collect. Use baseline from Phase 1 for comparison. Document results in phase file and STATUS.md.
+```
+
+### Migration Testing Handoff
+```
+Continue MotoVaultPro migration testing. Check current phase file for test commands. Run 'make test' in Docker containers. Verify all feature capsules work correctly. Update phase file with results.
+```
+
+## 📝 Context Preservation Prompts
+
+### Full Context Refresh
+```
+I need full context on MotoVaultPro modernization. Read STATUS.md first, then current phase file. This project uses Modified Feature Capsule architecture with Docker-first development. Each feature is self-contained in backend/src/features/[name]/. Never install packages locally - everything in containers.
+```
+
+### Architecture Context
+```
+MotoVaultPro uses Modified Feature Capsules - each feature in backend/src/features/[name]/ is 100% self-contained with API, domain, data, migrations, external integrations, tests, and docs. Maintain this architecture during modernization. Use make dev, make test, make rebuild for Docker workflow.
+```
+
+### Technology Context
+```
+MotoVaultPro modernization researched: React 19 + Compiler for 30-60% performance gains, Express → Fastify for 2-3x API speed, TypeScript 5.4+ features, modern Docker patterns. All Context7 research complete - focus on implementation per phase files.
+```
+
+## 🎯 Specific Scenario Prompts
+
+### After Long Break
+```
+Resuming MotoVaultPro modernization after break. Check STATUS.md for current phase and progress percentage. Verify Docker environment with 'make dev'. Check current phase file for exact next steps. Run any verification commands listed.
+```
+
+### New Week Startup
+```
+Starting new week on MotoVaultPro modernization. Check STATUS.md dashboard for progress. Review last week's accomplishments in change log. Check current phase file for today's tasks. Update STATUS.md timestamps.
+```
+
+### Before Major Change
+```
+About to make major change in MotoVaultPro modernization. Verify current phase file has rollback procedures. Confirm Docker environment is working with 'make dev'. Check that git working directory is clean. Document change in phase file.
+```
+
+### After Major Change
+```
+Completed major change in MotoVaultPro modernization. Update current phase file with results. Test with 'make test'. Update STATUS.md progress. Check if ready to move to next phase or if more current phase work needed.
+```
+
+## 📊 Verification Prompts
+
+### Quick Health Check
+```
+Run quick MotoVaultPro health check. Execute 'make dev' and verify services start. Check 'make logs' for errors. Test frontend at localhost:3000 and backend health at localhost:3001/health. Report status.
+```
+
+### Phase Completion Check
+```
+Verify MotoVaultPro phase completion. Check current phase file - all checkboxes should be marked. Run verification commands listed in phase file. Test functionality. Update STATUS.md if phase is truly complete.
+```
+
+### Pre-Phase Transition
+```
+Prepare MotoVaultPro for next phase transition. Verify current phase 100% complete in phase file. Run final tests. Update STATUS.md with completion. Review next phase prerequisites in next phase file.
+```
+
+---
+
+**Usage Notes**:
+- Always include relevant context about Modified Feature Capsule architecture
+- Mention Docker-first development requirement
+- Reference that Context7 research is already completed
+- Point to specific phase files for detailed steps
+- Emphasize updating STATUS.md for progress tracking