Even with the same Claude, the accuracy and usefulness of its answers change a lot depending on how you write your prompt. A good prompt is not a hard skill — it starts with a few principles. Master these seven and your results will improve noticeably.
1. Be clear and specific
Instead of "summarize this," try "summarize the meeting notes below into 3 key decisions and action items per owner." The clearer you are about what and how, the more accurate the answer.
2. Provide enough context
Claude does not know your situation. Sharing the target reader, goal, field, and constraints leads to a much better fit — for example, "explain as if to a new hire with no marketing background."
3. Specify the output format
Decide length (e.g., 3 paragraphs), format (table, list, code), and tone (formal, friendly) up front to avoid rework. Try "as a table," "under 200 characters," or "as a numbered list."
4. Show examples
Showing one or two examples of the result you want (often called few-shot) helps Claude match the format and tone precisely. This is especially effective for repetitive, fixed-format tasks.
5. Break complex tasks into steps
For multi-step problems, asking Claude to "think step by step" improves accuracy. Splitting the process works better than asking for everything at once.
6. Assign a role
Setting a role (persona) such as "you are an experienced copy editor" aligns the answer's perspective and expertise with that role.
7. State what NOT to do
Spelling out what to avoid (e.g., "no jargon," "stick to confirmed facts, no guessing"), in addition to what you want, makes the result cleaner.
Bad vs. good example
❌ Bad: "Write a marketing post."
✅ Good: "Write an Instagram post promoting an eco-friendly tumbler for people in their 20s, in a friendly tone, within 3 sentences, including 5 hashtags."
Packing in the audience, goal, format, length, and constraints like the second example gets you close to the result in a single try.
Wrap-up: a prompt is a conversation
It does not have to be perfect from the start. If the answer falls short, refine it with follow-ups like "shorter," "add an example," or "make it a table." The key is to ask specifically and improve iteratively.