The short answer
Ask for a file-to-behavior map. Begin with read-only diagnosis when scope is unclear.
Try it in three steps
- Describe the current defect and desired behavior.
- Request planned files and exclusions.
- Check that validation reproduces the original issue.
A practice prompt
Before you start
Review a fictional change plan without coding.
Practice material (fictional)
Problem: phone menu will not open. Plan: fix event/state handling, change homepage colors and delete the image folder.Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.
Diagnose this broken button read-only. Provide evidence, minimal affected files and validation steps without redesigning the page.What to look for (not a recorded test result)
Event/state work may be relevant; color and deletion have no stated basis. Request a minimal fix and opening, closing and return checks.
If it goes wrong
Improve architecture is not a diagnosis; return to the concrete failure and evidence.
Check your result
You can explain user-visible effects rather than merely naming files.
References and scope
The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.