How to Write Good Prompts: The Basics
By Muhammad Asif · · 5 min read
Most people write prompts like search queries. A few simple changes make the results dramatically more useful.
Most people write prompts the same way they type a Google search. Short, vague, hoping the tool figures out what they meant. Sometimes that works. Often it does not, and the result is a frustrating output that you then have to rewrite yourself.
The good news is that writing better prompts is not a skill that requires a formal course. A few simple habits change the results noticeably.
The gap between what you type and what you mean
A prompt is an instruction. The assistant reads it literally, then does its best to guess what you wanted. The gap between what you typed and what you actually meant is where weak outputs come from.
A common example: someone types "write a product description for my soap." The result is a generic paragraph about moisturising and natural ingredients. What they actually wanted was a 60-word description in a playful tone for a specific gift set targeting people who love outdoor activities.
The assistant cannot read your mind. Everything it cannot infer, it fills in with the most common answer it has seen. Your job is to close as many of those gaps as possible before it starts writing.
The four things a good prompt usually includes
Role. Tell the tool who it is for the task. "You are helping a small business owner write a formal complaint letter." This shapes the vocabulary, tone, and assumptions the tool brings to the job.
Task. Say what you want, clearly. "Write a 100-word product description" is better than "write about this product." The more specific the instruction, the less the tool has to guess.
Context. Give the relevant background. What is the audience? What is the purpose? What do you already know that the tool needs to know?
Constraints. Say what you do not want. "Do not use technical jargon." "Do not exceed two paragraphs." "Do not suggest seeking professional advice." Constraints save a lot of editing after the fact.
You do not need all four every time. For simple tasks, two or three are enough. For complex work, using all four will get you much closer to a usable result on the first try.
What to do when the first result is not right
Do not start over. Add to the prompt. If the tone is too formal, say "make it more conversational." If it is too long, say "cut it to half the length." If it missed the point, say "focus on X, not Y."
Working in conversation is usually faster than rewriting the original prompt from scratch. Most tools keep the context from earlier in the conversation, so you are refining rather than repeating.
One useful habit: when you get a result you like, notice what you did differently in that prompt. Keep a small note of prompts that worked well. After a few weeks, you will have a set of patterns that work for your specific tasks.
Common mistakes that lead to weak outputs
Being vague about audience. "Write for a general audience" is too broad. "Write for someone who has never used a spreadsheet before" is specific and useful. The audience shapes the vocabulary, the assumed knowledge, and the level of explanation.
Asking for too many things at once. "Write a blog post, make it funny, include five examples, add a checklist at the end, and keep it under 500 words." Split complex requests into separate steps. Do the main writing first, then ask for the checklist, then ask for the final edit.
Forgetting to specify the format. If you want bullet points, say so. If you want a table, ask for a table. If you want numbered steps, specify it. The tool defaults to paragraphs if you do not say otherwise, which is not always what you need.
Giving no context about the purpose. "Write an email about the meeting" tells the tool almost nothing. Who is the recipient? Is this a reminder, a follow-up, or a request to reschedule? What tone is appropriate for this person and situation?
A before-and-after example
Weak prompt: "Write a social media post about my bakery."
Stronger prompt: "Write a short social media caption for a local bakery. The tone is warm and friendly. The post is about fresh cinnamon rolls available on Saturday morning. Keep it under 60 words and end with a simple call to action like visiting the shop."
The second prompt has a clear role implied (a local business), a specific task, context (cinnamon rolls, Saturday), and constraints (under 60 words, specific ending style). You will get a usable result much faster, and you will need to edit it less.
A note on iteration
The first output from any prompt is a draft. Treat it that way. The goal of a good prompt is not to get a perfect result in one shot. It is to get a result that is close enough to be worth refining. Each iteration gets you closer.
The more you use a particular tool for a particular task, the better your prompts will get for that combination. The patterns you discover are yours.
Key takeaways
- A prompt is an instruction; the more specific it is, the less the tool has to guess.
- Include role, task, context, and constraints; you do not need all four every time, but each one you add reduces guessing.
- When the first result is not right, add to the prompt rather than starting over.
- Avoid vague audience descriptions, too many requests at once, and forgetting to specify the format.
- Keep a note of prompts that worked well; patterns repeat across similar tasks.

