Use the agent to form and test hypotheses.
1. Reproduction first
Capture a minimal reproduction and relevant logs before proposing a fix. A guessed cause can lead to a plausible patch that changes nothing.
2. Hypothesis checks
Ask what observation would support or disprove each explanation. Run targeted checks and compare actual results with the hypothesis.
3. Android-specific tools
Use supported IDE and device inspection capabilities for lifecycle, rendering and runtime issues. A static code explanation cannot establish a device-only failure.
Worked scenario
A crash occurs only after process recreation. The agent must inspect restored state rather than changing a random null check in the initial screen path.
Apply it
Provide a failing reproduction, test one hypothesis and record why the evidence supports the chosen fix.
Check your understanding
The fix addresses a demonstrated cause rather than a coincidental symptom. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.