What System Prompts Are and Why You Should Care
A system prompt is the instruction set you give Claude before it starts responding to you. It is the difference between saying "hey Claude, write me a marketing email" and saying "you are a senior copywriter with 15 years of experience writing direct response emails for B2B SaaS companies. Your tone is conversational but professional. You always lead with the pain point, not the feature. Every email you write includes a clear call to action and is under 200 words."
The second version produces dramatically better output. Not a little better. Dramatically better.
System prompts work because they give Claude context about who it should be, how it should behave, and what the output should look like. Without a system prompt, Claude defaults to being a helpful generalist. With a good system prompt, Claude becomes a specialist tuned to exactly what you need.
How to Write an Effective System Prompt
Good system prompts share a few common elements. Here is the framework.
Define the role. Tell Claude who it is. "You are a senior full-stack developer specializing in Next.js and TypeScript" is better than "help me with code." The role sets the expertise level and perspective that Claude brings to every response.
Set the context. Give Claude the information it needs to do the job well. "You are helping a small business owner who is not technical and needs clear, jargon-free explanations" changes how Claude communicates. Without this, Claude guesses at the audience and often guesses wrong.
Specify constraints. Tell Claude what to do and what not to do. "Never use bullet points unless explicitly asked. Write in short paragraphs. Do not include disclaimers about consulting a professional." Constraints prevent the behaviors that make AI output feel generic.
Define the output format. If you want a specific structure, describe it. "Every response should include a one-sentence summary at the top, followed by the detailed explanation, followed by a section called 'What To Do Next' with specific action items." Format instructions ensure consistency.
Include examples when possible. Show Claude what good output looks like. "Here is an example of the tone and style I want:" followed by a paragraph in your voice is worth more than three paragraphs of abstract description.
Real System Prompts You Can Use
Here are system prompts that produce genuinely better output for common use cases. Copy and adapt them.
Business Email Writer
You are a senior business development professional writing emails for a B2B technology company. Your writing style is direct, warm, and confident. You never use corporate jargon, buzzwords, or filler phrases.
Rules:
- Every email is under 150 words unless asked otherwise
- Open with something relevant to the recipient, never with "I hope this finds you well"
- End with a clear, specific call to action
- Use short sentences and short paragraphs
- Match the formality level to the relationship described
- Never use exclamation points more than once per email
Technical Documentation Writer
You are a senior technical writer creating documentation for a developer audience. Your writing is precise, scannable, and example-driven.
Rules:
- Lead with the most practical information first
- Include code examples for every concept you explain
- Use second person ("you") not third person
- Keep paragraphs under 4 sentences
- Use headers and subheaders to make content scannable
- Assume the reader is competent but unfamiliar with this specific topic
- Never pad with unnecessary context or background
Content Strategist
You are a content strategist for an SEO-focused website. Every piece of content you create is designed to rank in Google search results and provide genuine value to readers.
Rules:
- Every article targets a specific search keyword or question
- Open with a direct answer to the question being asked
- Use H2 and H3 headings that match the way people search
- Include a FAQ section with questions people actually ask about this topic
- Write in a conversational, authoritative tone
- Never use filler phrases like "in today's world" or "it's important to note"
- Every paragraph must contain useful information, not padding
- Articles should be as long as needed and no longer
Sales Call Prep Assistant
You are a senior sales strategist helping prepare for prospect calls. You think like a buyer, not a seller.
When given information about a prospect, you provide:
1. The three most likely pain points based on their industry and company size
2. Questions to ask that uncover real problems (not leading questions)
3. Potential objections and how to handle each one
4. A suggested agenda for the call
5. One insight about their industry that shows you did your homework
Rules:
- Never suggest manipulative sales tactics
- Focus on understanding the prospect's situation, not pitching features
- Assume the prospect is smart and has seen every sales trick
- Keep all preparation materials under 500 words
System Prompts in the Claude API
If you are building applications with the Claude API, the system prompt goes in the system parameter:
const response = await fetch('https://api.anthropic.com/v1/messages', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'x-api-key': 'your-api-key',
'anthropic-version': '2023-06-01'
},
body: JSON.stringify({
model: 'claude-sonnet-4-20250514',
max_tokens: 1024,
system: 'You are a helpful customer service agent for an online store. Be friendly, concise, and solution-oriented. If you cannot resolve an issue, explain what the customer should do next.',
messages: [
{ role: 'user', content: 'I never received my order from last week.' }
]
})
});
The system prompt persists across the entire conversation and does not need to be repeated with each message.
System Prompts in Claude Projects
In the Claude web interface, Projects give you a way to set persistent instructions without using the API. Create a project, add your system prompt to the project instructions, upload any reference documents, and every conversation within that project will follow your instructions.
This is ideal for recurring workflows. Create a project for "Client Proposals," set the system prompt to define your writing style and proposal structure, upload your company branding guidelines, and every proposal you draft in that project starts from the same strong foundation.
Common Mistakes to Avoid
Being too vague. "Be helpful and professional" does nothing. Claude is already helpful and professional by default. Your system prompt should change behavior that would not happen otherwise.
Being too long. System prompts over 1,000 words start to see diminishing returns. Claude may de-prioritize instructions that appear later in a very long prompt. Keep it focused on the most important behaviors.
Contradicting yourself. "Be concise" and "provide comprehensive detail on every point" cannot both be true. Prioritize and be specific about when each behavior applies.
Not testing. Write the prompt, run five different queries through it, and see if the output matches what you want. Adjust based on what you observe, not what you assume.
The Bottom Line
System prompts are the single highest-leverage skill in using Claude effectively. The time you invest in writing a good system prompt pays dividends across every interaction. A ten-minute investment in crafting the right prompt can save hours of editing and re-prompting over the course of a project.
Start with one of the templates above, adapt it to your specific needs, and iterate from there.