A broad prompt can produce a polished response while leaving the real task unresolved. The model needs useful context, but the person reviewing the answer also needs a clear account of what was requested.
State the job, the relevant input, and the expected form of the result. Include important constraints and explain what should remain unknown rather than filled in. A small example can clarify a format or tone that is otherwise difficult to describe.
Review the output against the request and revise the prompt around the first meaningful mismatch. A longer prompt is not automatically a better one. The practical goal is a clear task and a result whose quality can be inspected.
- State the job and relevant input.
- Describe the expected result.
- Leave unknown facts explicit.
Picture this situation.
A rewriting task can specify its audience, length, and required facts. Those details explain the intended work more clearly than asking for a better version.
A second way to look.
Define the task before judging the answer. A fluent response can satisfy the shape of a request while missing a constraint that matters to the work.
Follow a related question
Connect access to a visible action.
Ask at the right momentSeparate time-sensitive information from routine updates.
Notifications with a reason to arriveKeep learning
Related background to continue exploring this subject.
Google: prompt design strategies Google: an introduction to language models
