What is the COSTAR Framework?
COSTAR is a six-component prompt engineering framework designed for content creation, communication tasks, and AI system prompt design. The acronym stands for Context, Objective, Style, Tone, Audience, and Response — covering every major dimension that determines not just what an AI says, but how it says it.
- C — Context: Establish the operating situation
- O — Objective: Define the communication goal
- S — Style: Specify the writing structure and format approach
- T — Tone: Set the emotional register
- A — Audience: Characterize the reader precisely
- R — Response: Define the output format and constraints
The framework has become particularly popular in Claude and GPT system prompt design because it provides a complete specification language for AI assistant behavior. When you are configuring an AI assistant to work consistently across many different user inputs, COSTAR gives you the vocabulary to define every relevant parameter: the operating context, the goal, the writing style, the emotional register, the target reader, and the output format.
What distinguishes COSTAR from frameworks like RISEN or QUEST is its explicit separation of Style and Tone as independent components. Most frameworks treat these as a single "voice" parameter. COSTAR recognizes that the structural and technical aspects of writing (style) are distinct from the emotional register (tone) — and that getting both right simultaneously is what makes communication land with a specific audience.
When to Use the COSTAR Framework
AI System Prompts
Configure Claude, GPT, or Gemini assistants with a complete behavioral specification — COSTAR covers every dimension that shapes consistent, on-brand assistant behavior.
Marketing & Brand Content
Produce on-brand copy for a specific audience — social media posts, email campaigns, ad copy — where style, tone, and audience targeting are as important as the message itself.
Long-Form Content
Blog posts, whitepapers, and thought leadership articles where the style and audience calibration determine whether the content resonates or falls flat.
Customer Communication
Support responses, onboarding emails, and user-facing notifications where the tone must be precisely calibrated to the audience and context.
Speechwriting & Presentations
Scripts, keynote talks, and executive presentations where the audience, tone, and style must be adapted to a specific speaker and occasion.
Multi-Channel Content
Adapt a single piece of content across channels — LinkedIn, email, website — by changing the Response component while keeping Context, Objective, and Audience consistent.
How to Use the COSTAR Framework
- 1
Context — Establish the operating situation
Describe the situation the model is operating in: what product or service it represents, what the user relationship is, what has happened before this interaction, and any domain-specific knowledge the model should have. Context is the foundation everything else builds on.
- 2
Objective — Define the communication goal
State precisely what the output should achieve — inform, persuade, support, entertain, or convert. Go beyond the topic to the intended effect: "Help users solve problems quickly" is a better Objective than "Answer user questions about the product."
- 3
Style — Specify the writing structure and format approach
Define the structural and technical characteristics: formal or casual, dense or scannable, long-form or brief, technical or accessible. Include specific constraints like "use numbered steps for procedures" or "lead with data before explanation."
- 4
Tone — Set the emotional register
Specify the emotional quality of the writing: authoritative, empathetic, playful, urgent, warm, direct. Distinguish tone from style — you can be formal in style while being warm in tone. List specific words or phrases to avoid if tone calibration is critical.
- 5
Audience — Characterize the reader precisely
Define who will read the output in specific terms: role, industry, expertise level, what they care about, and what their biggest frustrations or goals are. The more specific your Audience definition, the more precisely the model can calibrate vocabulary, examples, and depth.
- 6
Response — Define the output format and constraints
Specify the format, length, structure, and any platform-specific constraints. Include document type (bullet list, numbered steps, essay), word count, heading structure, and any elements that must or must not appear in the output.
Prompt Examples
Context: You are the AI assistant for Meridian, a B2B project management SaaS platform. Users are project managers and team leads at professional services firms. They use the platform daily and have intermediate to advanced familiarity with project management concepts. They typically contact support when something is blocking their work or when they cannot find a feature. Objective: Help users solve their problems quickly and completely. When a solution exists, provide it clearly and directly. When a limitation exists, acknowledge it honestly and offer the best available workaround. Style: Clear, direct, and practical. Use numbered steps for procedural answers. Use bullet points for options or comparisons. Avoid marketing language, filler phrases, and unnecessary caveats. Never say "Great question!" or "Certainly!". Tone: Professional and efficient, with warmth. Users are busy — respect their time. Be empathetic when they are frustrated, but do not dwell on apologies. Get to the solution quickly. Audience: Project managers and team leads at professional services firms. Assume familiarity with project management terminology but do not assume engineering knowledge. Use plain language for anything technical. Response: Keep responses under 250 words unless a step-by-step process genuinely requires more. Always end with a follow-up offer: "Let me know if you need help with anything else" or similar. Format code or settings paths in inline code format.
Context: This prompt is for a weekly LinkedIn post series about sustainable business practices for a B Corp certified management consulting firm. The series is called "The Responsible Business Brief" and runs every Tuesday. Previous posts have covered supply chain transparency, DEI measurement, and carbon accounting. Objective: Write a LinkedIn post for this week's topic — the business case for living wages. The post should inform, provoke thought, and position the firm as a credible, practitioner-led voice in the responsible business conversation. Style: Thought leadership essay style, compressed for social media. Lead with a counterintuitive observation or a data point. Use short paragraphs (2–3 sentences maximum). No bullet points. One clear call-to-action or question at the end to prompt comments. Tone: Confident and authoritative, but not preachy or activist. Speak from a business-outcomes perspective, not a moral-obligation perspective. The audience already cares about sustainability — the firm's job is to show them how to build the business case, not to convince them why they should care. Audience: CEOs, CFOs, and Chief People Officers at mid-to-large companies actively working on or interested in ESG and responsible business practices. Sophisticated, time-poor, skeptical of hype. They respond to data, case studies, and pragmatic frameworks. Response: 180–220 words. No hashtags in the body of the post — add 3–5 relevant hashtags as a separate line at the end. Include a specific data point or statistic to anchor the business case.
Pros and Cons
| 🟢 Pros | 🔴 Cons |
|---|---|
| Separates Style and Tone as independent components — a precision other frameworks lack | Less suited for analytical or research tasks where communication style is not the primary variable |
| Ideal for system prompt design — covers every dimension of persistent AI assistant behavior | Style and Tone components can overlap, requiring care to keep them distinct |
| Audience component enables precise vocabulary and depth calibration | Six components add overhead for simple content requests where fewer parameters suffice |
| Response component ensures output format is always explicitly specified |
Frequently Asked Questions
What does COSTAR stand for in prompt engineering?
COSTAR stands for Context, Objective, Style, Tone, Audience, and Response. It is a six-component framework designed for content creation, communication, and audience-targeted writing. It is particularly popular for Claude and GPT system prompt design because it covers every major dimension of how a response should be written, not just what it should cover.
Why is COSTAR especially popular for system prompts?
System prompts need to establish a persistent operating mode for an AI assistant across many different user inputs. COSTAR covers every relevant dimension: what the assistant knows (Context), what it is trying to achieve (Objective), how it writes (Style and Tone), who it is writing for (Audience), and what its output should look like (Response). This comprehensiveness makes it the go-to framework for configuring AI assistants.
What is the difference between Style and Tone in COSTAR?
Style is the structural and technical dimension of writing — formal vs. casual, technical vs. accessible, dense vs. scannable, long-form vs. brief. Tone is the emotional register — empathetic, authoritative, playful, urgent, reassuring. You might write in a formal style with a warm tone, or in a casual style with an urgent tone. Both dimensions are independent and together they define the full voice of the output.
How specific should the Audience component be?
The more specific your Audience definition, the more the model can calibrate its vocabulary, assumed knowledge level, and the examples it uses. 'Business professionals' is too vague. 'Finance Directors at mid-market B2B companies who are familiar with SaaS metrics but have no engineering background' allows the model to make precise choices about jargon, analogy selection, and depth of explanation.
What goes in the Response component?
Response defines the format and structure of the output: length, document type (bullet list, numbered steps, essay, table, JSON), section headings, and any formatting constraints. If you are building for a specific platform — a chat interface, a web page, a PDF report — the Response component is where you specify the constraints that make the output fit that context.
Can COSTAR be combined with role prompting?
Yes — COSTAR and Role Prompting are highly complementary. You can begin your system prompt with a role definition ('You are a senior product marketing manager...') and then use COSTAR to specify the Context, Objective, Style, Tone, Audience, and Response for that role. The combination produces very consistent, well-characterized AI assistant behavior.
Is COSTAR better than RISEN or CRISPE for system prompts?
COSTAR's advantage over RISEN is its Style and Tone components, which make it particularly strong for content-heavy or communication-focused tasks. CRISPE adds a persona and voice component that overlaps with COSTAR's Style. For system prompts where the communication style, audience targeting, and output format are the primary variables, COSTAR is often the most precise fit. For task-oriented assistants, RISEN's Steps component offers stronger procedural control.