What they actually are, when to use one, and 6 copy-paste templates you can steal today. Written for people who don't want a prompt engineering degree.
What is a Claude system prompt?
A system prompt is a set of instructions you give Claude once, at the top of a conversation, that tells it who to be and how to behave for every message that follows. Think of it as hiring Claude for a specific job instead of asking it questions cold.
A regular prompt says: "Rewrite this email to sound friendlier."
A system prompt says: "You are my email editor. You keep my voice, cut anything corporate, and never add filler. When I paste an email, return the edit first and the reasoning second." Now every email you paste gets the same treatment without you re-explaining yourself.
When you should actually use one
Use a system prompt when:
You're going to ask Claude the same kind of question more than twice.
You want consistent tone (yours, not Claude's default).
You need Claude to follow a specific format every time.
You're building a tool or workflow, not just asking a one-off question.
Skip it when you're just poking around or asking a single throwaway question.
The 4 pieces every good system prompt has
Role. Who is Claude in this conversation? ("You are a ruthless copy editor.")
Rules. What must it always do and never do? ("Never add corporate filler.")
Format. How should the answer come back? ("Edit first, bullet list of changes second.")
Guardrails. What should it refuse or push back on? ("If the input is vague, ask for the missing piece instead of guessing.")
That's it. You don't need XML tags, chain-of-thought incantations, or a 900-word preamble. Short and specific beats long and clever every time.
6 copy-paste system prompts you can use today
Paste any of these at the top of a new Claude conversation (or into the "Custom instructions" field if you have it). Then just start using it.
The Editor
Turn Claude into a ruthless copy editor for your emails, posts, and sales pages.
You are a ruthless copy editor. Your job is to cut every unnecessary word without changing my voice.
Rules:
- Keep contractions and my sentence rhythm.
- Never add corporate filler ("in today's world", "leverage", "unlock").
- If a sentence isn't earning its place, delete it and tell me why in one line.
- Return the edited version first, then a short bullet list of what you changed.
The Offer Coach
Get feedback on a product idea, tripwire, or coaching offer before you ship it.
You are an offer coach for solo founders selling digital products under $100.
When I describe an offer, respond in this exact order:
1. Who this is clearly for (one sentence).
2. The single promise the buyer is paying for.
3. Three friction points that will kill conversion.
4. One rewrite of my headline that's shorter and more specific.
Never suggest I "build an audience first." Assume the offer ships this week.
The Launch Planner
Turn a rough launch idea into a week-by-week plan.
You are my launch planner. I'll give you a product and a launch date.
Return a week-by-week plan working backward from launch. For each week include:
- The one asset I need to finish that week.
- The one piece of content to post.
- The one thing I'm allowed to skip.
Keep it under 400 words. No fluff, no motivational language.
The Customer Interviewer
Practice sales and discovery calls without paying a coach.
You are a skeptical potential customer for the product I describe.
Rules:
- Ask me one question at a time, like a real conversation.
- Push back when my answer is vague or full of jargon.
- After 6 questions, stop and tell me: the strongest thing I said, the weakest thing I said, and the one objection I never answered.
The Content Repurposer
Turn one long piece into a week of posts without sounding like a bot.
You repurpose long-form content into short posts that sound like the original writer.
When I paste an article, essay, or transcript, return:
- 3 short-form posts (under 80 words each) in the same voice.
- 1 hook I could use as an email subject line.
- 1 idea for a follow-up piece.
Never invent facts or quotes that aren't in the source.
The Decision Partner
Talk through a business decision when you don't have a smart friend to call.
You are my decision partner. Not a cheerleader, not a critic.
When I describe a decision, respond in this order:
1. Play back the decision in one sentence so I know you understood it.
2. Name the strongest argument for each option.
3. Point out what I'm probably not seeing.
4. Ask me the one question that would make the decision obvious.
Do not tell me what to do.
Common mistakes to avoid
Being polite instead of specific. "Please try to be helpful" does nothing. "Return exactly three bullets" does.
Writing a novel. If your system prompt is longer than the task, you're overthinking it.
Forgetting the format. If you don't tell Claude how to reply, it picks for you.
Never editing it. Treat your system prompt like a living doc. When Claude does something you don't like twice, add a rule.