Get a usable answer by stating role, task, and format
prompting basics
// what it does
Naming a role, the exact task, the output format, and any constraints removes the guesswork that produces generic answers. The role sets vocabulary and depth, the format pins the shape of the reply, and constraints like length, audience, and what to avoid keep it on target. This one structure carries across almost every prompt you write.
// prompt
> Act as a senior UX writer. Rewrite the onboarding screen below for first-time users: plain, encouraging, max 40 words, no jargon. [paste text]> You are a tax accountant. Explain the difference between a Roth and a traditional IRA to a 25-year-old, in 4 short bullet points.// gotcha
Precise beats long. A vague "write about X" invites filler; a role plus a concrete deliverable ("as a UX writer, write a 40-word...") gives the model something to aim at and something to be judged against.