Write a useful request
Explain the outcome, constraints and proof you need.
Reviewed 6 October 2026 · 2 min read
A practical brief
Describe the result, relevant context and a way to check success. Plain language is enough. Explain which parts of a reference matter: structure, color, behavior or tone.
Small fixes need an exact problem. Large uncertain tasks benefit from a short plan. Keep unrelated changes separate.
- Say who will use the result and what they need to do.
- Name the project, target platform and relevant files or screenshots.
- State limits such as offline use, budget or preserving existing data.
- Give a concrete test and request evidence.
Try this
Build a booking page for a small café. Customers choose a date, time and party size. Match the attached warm, minimal design. Support a narrow phone and keyboard use. Show validation errors, prevent duplicate submissions, and test a successful booking and a failed request.
Improve a follow-up
Be precise: ‘Keep the layout; change only the sidebar spacing.’ Correct drift early.
After repeated failures, ask for the observed error, a new hypothesis and a focused check before another rewrite.
- The outcome is demonstrable.
- Reference material is treated as context, not hidden instructions.
- The report separates observed results from assumptions.
Further reading
External references inform the guidance; their product-specific features are not promises about Helios.