Use ARCHITECT-PLAN.md as the communication hub between the two Claude instances, following Claude Code best practices for multi-instance coordination.
cd /Users/junaid/dashboard-refactor/next-keystone-starter
claude-codeInitial Prompt for Architect:
Please read CLAUDE.md and begin analyzing the refactoring requirements for [specific component/feature]. Follow the instructions in ARCHITECT-PROMPT.md for your role as the strategic architect.
cd /Users/junaid/dashboard-refactor/next-keystone-starter
claude-codeInitial Prompt for Editor:
Please read ARCHITECT-PLAN.md and confirm if you're ready to begin implementation. Follow the instructions in EDITOR-PROMPT.md for your role as the implementation specialist.
CLAUDE.md- Project guidance and patterns (existing)ARCHITECT-PROMPT.md- Architect role instructionsEDITOR-PROMPT.md- Editor role instructionsARCHITECT-PLAN.md- Living communication document (created by Architect)
- Architect reads CLAUDE.md and creates initial analysis in ARCHITECT-PLAN.md
- Architect develops complete refactoring strategy and marks "READY_FOR_EDITOR"
- Editor reads ARCHITECT-PLAN.md and begins implementation
- Editor updates progress in ARCHITECT-PLAN.md after each step
- Architect monitors progress and provides course corrections as needed
- Separation of Concerns: Strategy vs Implementation
- Component Extraction Focus: Specialized for breaking down monolithic components
- Quality Assurance: Each Claude reviews the other's work
- File-Based Communication: Clear handoffs and progress tracking
- CLAUDE.md Integration: Follows project-specific patterns and commands