03 / Understand the project
Start with the map, then make the move.
More context is useful only when it answers the task. Build a compact map of the path from user action to application behavior. Begin with read-only inspection, and ask the assistant to identify what it knows and what it still needs to confirm.
Follow the behavior through the repository
For a settings change, inspect the route, the settings component, the persistence boundary, and one nearby test. Note which module owns validation. Include project instructions and package scripts. A focused set of source references helps the assistant reuse the system instead of guessing from filenames alone.
Separate findings from assumptions
A file named cache does not prove that data is cached in production. Ask for file paths and the symbols that support each conclusion. Record missing context as an open question. Never include credentials or production customer records just to make a prompt feel complete; sanitized examples usually explain the relevant structure.
A starting prompt
Read the project instructions and package scripts. Trace how a settings value reaches storage. List the relevant files and existing conventions. Label assumptions explicitly. Do not change files.