FIELD GUIDE / 01
Your prompt needs a finish line.
“Make this better” is a starting point. “Make this easier for a first-time customer to understand” is a job.
Name the thing you want back
Ask for a launch email, a test plan, a comparison table or a short explanation. A concrete output gives you something to evaluate. If the request has several unrelated jobs, separate them.
Give it enough context to be useful
Explain who the result is for and what they already know. Include the relevant facts. Do not assume a model knows your product, your codebase or the conversation you had yesterday.
Make the constraints visible
Length, tone, required details and excluded topics can matter. “Keep it under 150 words, avoid hype and include one link” is easier to act on than “make it professional.” Conflicting instructions still need a human decision.
Task: Write a launch email for AIGoblin.org. Audience: Curious makers trying the workshop for the first time. Context: Four browser-based tools. No account or model API required. Format: Subject line, short body, one call to action. Constraints: Under 150 words. No invented features or traffic claims.
Check the result, not just the prompt
Clear instructions do not guarantee correct answers. Verify facts, test code and review important claims. The Prompt Check tool detects structural cues; it cannot certify accuracy, safety or how a particular model will respond.