Function getDebugInstructions

src/index.ts:37–95

(debugUrl: string)

}

function getDebugInstructions(debugUrl: string): string {
  return `
## Debug Mode Instructions

You are now in DEBUG MODE. Your task is to instrument the codebase with fetch calls to capture runtime data for debugging.

### Workflow:
1. **Analyze the issue** - Understand what the user is trying to debug
2. **Identify key locations** - Find functions, handlers, or code paths relevant to the issue
3. **Insert fetch calls** - Place debug fetch calls at strategic points to capture:
   - Function inputs/outputs
   - State changes
   - Error conditions
   - Control flow branches
4. **Hand back to user** - Let them reproduce the issue
5. **Read logs** - Use debug_read to analyze the captured data

### Fetch Call Pattern:
\`\`\`javascript
${generateFetchSnippet(
  debugUrl,
  "descriptive-label",
  "{ variable1, variable2 }"
)}
\`\`\`

### Best Practices:
- Use descriptive labels like "user-login-start", "api-response", "error-caught"
- Capture relevant variables in the data object
- Place calls at function entry/exit points
- Add calls before and after async operations
- Capture error objects in catch blocks
- Don't forget to capture the state you're debugging

### Examples:
\`\`\`javascript
// At function entry
${generateFetchSnippet(debugUrl, "processOrder-entry", "{ orderId, items }")}

// Before async call
${generateFetchSnippet(debugUrl, "api-call-start", "{ endpoint, payload }")}

// After async call
${generateFetchSnippet(debugUrl, "api-call-complete", "{ response, status }")}

// In catch block
${generateFetchSnippet(
  debugUrl,
  "error-caught",
  "{ error: err.message, stack: err.stack }"
)}

// State changes
${generateFetchSnippet(debugUrl, "state-updated", "{ prevState, nextState }")}
\`\`\`

### Debug URL: ${debugUrl}
`;