Ask for better results
Write specific requests with existing examples, acceptance criteria, boundaries and a clear definition of done.
Replace broad requests with observable outcomes
The image contrasts "add validation" with a concrete description of what must be accepted and rejected. State the affected endpoint or component, expected behavior and error handling. Avoid vague requests such as "make it work."
Point to prior art
Identify relevant source files, utilities and tests so the agent can follow existing patterns. Explain which example is authoritative and where it does not apply.
Define done using acceptance criteria: valid input succeeds, invalid input receives a clear error, related tests cover the behavior and documentation reflects the change.
Keep scope small and state constraints
Ask for one coherent outcome rather than an entire subsystem. Say what must not change, such as a database schema or public contract. If a necessary change crosses that boundary, require the agent to stop and request a decision.
Good prompts improve direction. They do not replace review, test evidence or permission controls.