How to Write Better Prompts: A Practical Framework

Every week I run the same experiment. I ask five people to prompt a chatbot with the same task — "write me a cold email to a SaaS founder" — and five tabs produce five beige, corporate-sounding emails. Then one person adds three short lines of context, and their draft reads like a human wrote it. Same model, same request — the only variable was the prompt.

Prompting is not magic and it is not a programming skill. It is closer to briefing a fast, literal intern who has read most of the internet and knows nothing about you or whoever will read the output. A sloppy brief gets the statistical average of the web; a sharp one gets something genuinely good. If you have bounced between the best free AI tools that are actually worth your time and concluded they are all "fine but not amazing," the bottleneck may be your brief.

Why most prompts fail: the vending machine problem

Most people treat prompting like a vending machine: drop in a two-word request, press the button, take whatever drops out. When the result is mediocre they blame the model. Usually it did exactly what was asked — a thin ask leaves every gap to be filled by the model's defaults, and those defaults are boring on purpose.

Three failure modes cover most bad outputs:

• No context. The model does not know your product, your reader, or last week's decisions. It fills the vacuum with generic filler — filler that fits every company was, in effect, written for no one.
• No objective. "Write about X" never says what success looks like. Persuade? Explain? Summarize? The model hedges, covers everything, and hedging reads as padding.
• No format. You wanted three bullets; you got five paragraphs and a fake conclusion. The content may be fine — but it is the wrong shape, so you regenerate anyway.

CO-STAR fixes all three by forcing you to answer six questions before you hit enter. It takes about 40 seconds and, in my use, replaces five to ten minutes of "no, not like that" corrections.

The framework: CO-STAR

CO-STAR stands for Context, Objective, Style, Tone, Audience, and Response format — six labeled lines above your actual request. Use all six until the habit sticks; then drop whatever feels redundant.

C — Context: everything the model cannot guess

Context is what exists only in your head: what the project is, what happened, what you tried, what constraints apply. It is the highest-leverage line — when an output feels generic, missing context is almost always why. The test: if a smart colleague would need to be told it, so does the model. Two or three sentences plus the real material — the actual error, the actual draft — beats any description.

O — Objective: the one job of this prompt

State a single, finishable goal. "Write a homepage blurb whose job is to start the free trial" gives the model something to optimize for; "write something about our app" does not. Want three different things? Write three prompts — mixed objectives produce output that is adequate at everything and great at nothing.

S — Style: the genre you want back

Style is the form: a how-to post, a cold email, a changelog, a table. Naming the genre lets the model borrow its conventions instead of inventing hybrids. Concrete references beat adjectives — "like a Stripe docs page" says more than "professional and informative."

T — Tone: how it should feel

Tone is the attitude: direct, warm, skeptical, a little wry. Skip it and you get the default — neutral-professional, fine for internal notes, fatal for customer-facing copy. Two or three adjectives maximum; longer lists average out into mush.

A — Audience: who is actually reading this

The audience line turns a correct answer into a useful one. "Engineers debugging at 2 a.m." and "a non-technical marketing director" need the same facts in different vocabulary, depth, and pacing. If you adopt one improvement from this post, make it this: name the reader.

R — Response format: the shape of the deliverable

Say exactly what to hand back: a table with these columns, five bullets under 15 words each, 120 words with one headline. Format is the cheapest quality win available — one sentence that kills the most common reason people regenerate. Pasting the result into another tool? Name that tool's format too.

Before and after: three real examples

Example 1 — the product description

Before: "Write a product description for my project management app." What comes back: "Streamline your workflow and boost productivity with our powerful, intuitive platform." Not wrong — just nothing. It would fit a to-do app, a CRM, or a printer.

After: "Context: I run a bootstrapped project management app for freelance designers; most users came from spreadsheets. Objective: one homepage description whose only job is to start the free trial. Style: plain-English marketing copy, short sentences. Tone: confident, zero buzzwords. Audience: solo freelancers still tracking deadlines in spreadsheets. Format: one headline under 8 words plus a 60–75 word paragraph, no bullets, no exclamation marks."

That takes 45 seconds and produces an editable draft instead of a placeholder.

Example 2 — the meeting transcript

Before: "Summarize this meeting transcript." You get a polite paragraph recap that buries the two decisions that matter. Many teams now let the best AI note-taking tools capture every call automatically — the summary is where the information goes to die.

After: "Context: a 45-minute client call; I'm sending notes to the client's VP tomorrow. Objective: notes the VP can skim in 30 seconds and forward without editing. Style: clipped bullets. Tone: neutral and factual. Audience: a busy VP who hates surprises. Format: four sections — Decisions (owner + date), Action items (owner + deadline), Open questions, Risks. Quote figures and dates verbatim. Under 250 words."

Same transcript, different artifact: one is a recap for you; the other survives being forwarded. The "quote figures verbatim" line alone prevents the classic AI failure of rounding a number nobody will check.

Example 3 — the cold email

Before: "Write a cold email to a SaaS founder about our AI reporting tool." Expect "I hope this email finds you well," then three paragraphs that could be sent to anyone, including the founder's dog.

After: "Context: our tool turns raw product analytics into a weekly investor-ready update; Maya runs a 12-person devtools startup and builds these updates by hand on Sunday nights. Objective: get a reply, not a sale — book a 15-min walkthrough. Style: a personal email under 120 words. Tone: direct, no pressure. Audience: a technical founder who deletes templated outreach on sight. Format: subject under 6 words, four short paragraphs, one specific observation about her situation, one clear call to action, plus a PS offering the template free."

That is the experiment from the top of this post, written out: the old prompt carried maybe 15 bits of information, this one carries a hundred — each one removes a guess the model would make badly.

CO-STAR vs. two other prompting styles

CO-STAR is not the only framework in circulation. Here is how it sits against the two styles most people choose between:

Prompting style	What it looks like	Best for	Where it falls down
Plain zero-shot	"Write a 200-word product description for X"	Quick drafts you will rewrite anyway	Generic voice, no audience, format by chance
CO-STAR structured	Six labeled lines above the request	Customer-facing copy, anything with a specific reader	Overkill for one-liners; slows rapid brainstorming
Chain-of-thought	"Think through this step by step before answering"	Math, logic, debugging, many interacting constraints	Verbose on simple tasks; helps reasoning, not voice

Honest note: the labels matter less than they look — one context line already lifts plain zero-shot, and chain-of-thought drops inside a CO-STAR prompt for analytical tasks. Overlapping tools, not competing religions.

Where the framework bends

Models reward structure differently. In our head-to-head testing of the big three (see the ChatGPT vs Claude vs Gemini comparison), all three handle labeled CO-STAR blocks well but differ on how strictly they honor format constraints. If a model keeps ignoring your format line, repeat the constraint at the very end of the prompt — it usually works.

Agents multiply the stakes. A one-shot chat wastes only your words; an agent executes your intent across a dozen steps, so a vague objective compounds. If you are wiring prompts into automation, read our step-by-step guide on building an AI agent workflow first — the six fields become the skeleton of every agent task.

Who this framework is NOT for

CO-STAR is a briefing tool, and briefings are bad at some jobs. Skip it, or trim it heavily, when:

• You are brainstorming, not producing. Exploratory chats need looseness; six labeled fields turn a creative session into a procurement process.
• The task is under a minute of work. Fixing a typo, translating a sentence, checking a formula — writing a six-line brief takes longer than doing it.
• You cannot describe what "good" looks like. Style and audience lines require domain judgment. For legal reasoning, math proofs, or unfamiliar formats, chain-of-thought ("show your reasoning, then the answer") beats any style framing.
• You already have a tuned system prompt. If you routinely paste long reusable instructions into a chat, you have internalized CO-STAR — you just call it "my usual preamble."
• The medium is voice or chat apps. Dictating six labeled sections into a voice assistant is friction with no payoff; one context and one format sentence get most of the benefit.

The one trap: framework enthusiasm. People fill all six fields for tasks that need two, then blame the framework. The fields are a checklist, not a liturgy.

Honest verdict

CO-STAR is worth learning, with three qualifiers.

The acronym is not magic. RACE (Role, Action, Context, Expectation), CRISPE and half a dozen cousins cover the same ground with different letters — but all of them force the same trio: context, audience, format. That trio does roughly 80% of the work; the rest matters mostly for customer-facing copy.

The payoff is uneven, and you should expect that. For emails, landing pages, docs, and summaries — anything with a human reader — structured prompts cut my regeneration loops to about a third of what bare prompts produced. For math, debugging, and multi-step reasoning, the same structure changes little; reasoning instructions matter more than framing.

It is a ladder you are meant to kick away. After a month of CO-STAR, context-and-format become reflexive and the six-line block starts feeling slow. That is the point: once the habit of briefing the model like a colleague is in, delete the scaffolding.

Bottom line: if your AI outputs feel generic, the fix is probably free. Write the six lines before you switch anything — and watch the same model suddenly sound like it knows what you want. Because this time, it does.

Keep reading

• ChatGPT vs Claude vs Gemini: an honest 2026 comparison
• The best free AI tools that are actually worth your time
• How to build an AI agent workflow, step by step
• Best AI note-taking tools compared: 2026

Questions? Email nandminc2020@gmail.com