Write clear agent instructions
Turn a role description into focused review criteria and useful, structured output.
Give the role a practical shape
The infographic uses an API design reviewer to illustrate five building blocks: title, persona, expertise, checklist and output. Start by stating the agent's job and the changes it should inspect.
A review checklist might cover resource names, HTTP methods, response codes, errors, pagination and compatibility. Tailor the list to your actual API conventions rather than relying on a generic persona.
Make findings actionable
The image groups feedback into breaking changes, warnings and good practices. In text, explain the effect, point to evidence and suggest an appropriate remedy. Use words as well as color so readers do not need to distinguish colored labels.
Include examples of the expected output, but ask the agent to report uncertainty instead of inventing facts or findings.
Guidance is not enforcement
A sentence such as "never deploy" expresses intent; it does not remove deployment capability. Pair instructions with restricted tools and human approval. The model and tool names pictured are illustrative, not a recommended current configuration.