By Alberto Alatorre ·
How do I write prompts that get usable results?
A usable prompt has three things: real context, the exact output you want, and an example of good. Length is less of a problem than vagueness. That comes from Cork Ai Consulting, August 18, 2026, and it is the shortest honest advice on prompting there is. Most bad output is not a tool problem. It is a vague prompt problem. The tool did what you asked. You asked for something vague.
What is the structure?
Use five parts, and keep each one short. Task, Context, Audience, Format, and Tone and limits. That structure comes from Herby Design, updated about November 10, 2026, and it fits in one short paragraph. You do not need a template library. You need the five parts, every time.
Task is the job, in one sentence. Write a reply, draft a quote, summarize this thread. Context is the real detail the tool needs: who the customer is, what they asked for, what has already been agreed. Audience is who will read it, a customer, a vendor, your own team, because the same words land differently on each. Format is the shape: three sentences, a bullet list, a table. Tone is the voice: plain, warm, firm. And limits are what the output must not do: no prices you have not confirmed, no promises you have not made, no jargon.
A prompt with all five parts is rarely more than a paragraph. A prompt without them is a wish.
What does a good prompt look like?
Here is a bad one. "Write an email to a customer about their quote." The tool does not know the customer, the job, the price, or the tone. It will invent all four, and three of them will be wrong.
Here is the same prompt with the five parts. "Task: draft a reply to a customer. Context: the customer is [customer name], she asked for a quote on a website redesign, and we quoted [price] with a [timeline]. Audience: [customer name], a small business owner, not a technical person. Format: three short paragraphs, plain language. Tone: warm and direct. Limits: do not change the price or the timeline, and do not promise anything extra."
The second prompt is longer, but it is not long. It is specific. Specificity is the whole skill. The tool can only work with what you give it, so give it the facts and let it do the writing.
What should never go into a prompt?
Private customer or business data. Use placeholders instead of sharing private details, and review claims, details, and tone before publishing or sending Ai output. That guidance also comes from Herby Design, and it is the part people skip most often. A prompt is not a private notebook. Anything you paste in can be stored, reviewed, or used to train a model, depending on the plan you are on. Use a placeholder like [CUSTOMER NAME] and fill in the real name after the draft comes back. It takes five seconds, and it keeps private data out of the tool.
The same applies to prices, dates, and promises. The tool should not be the place where a price is decided. The price is decided by you, and the prompt carries it in.
How do you fix a bad first draft?
With one focused follow up, not a new prompt. Name the one thing that is wrong, give the correction, and ask for the draft again. "This is too formal. Make it warmer and cut it to three paragraphs." "You changed the price. The price is [price]. Keep it." "This is too long. Keep the first paragraph and cut the rest."
One fix at a time. If you list five fixes at once, the tool will fix three and forget two, and you will be back where you started. The follow up is where prompting actually happens. The first draft is a starting point, not a finished product, and a good follow up is worth more than a perfect first prompt.
That is the gap most prompt libraries miss. They sell copy paste prompts, but they do not teach the follow up. A library prompt will never fit your customer, your price, or your tone. A follow up will, because you are the one giving the correction.
What is the habit?
Write the prompt with the five parts, read the draft, fix it with one follow up, and check the prices, dates, names, and promises before it goes out. That is the whole habit. It takes a minute longer than the vague prompt, and it saves the ten minutes you would spend fixing the output afterward.
What to do next
Take one email you write every week, a reply, a quote, a follow up, and write the next one with the five parts. Task, Context, Audience, Format, Tone and limits. See what comes back. If you want the basics taught properly, Ai 101 covers prompting in about 15 minutes, free, with no signup, in English and Spanish.
Ai 101: prompting, ChatGPT and Gemini basics, and Ai limits, free