Claude Prompt Templates by Job Role — Dev, Marketing & Planning

A prompt — the instruction you send to Claude — shapes the quality of what you get back. Writing one from scratch every time, though, takes effort you could spend elsewhere. This guide collects copy-paste-ready Claude prompt templates for three common roles: developers, marketers, and planners. Just swap out the bracketed placeholders and send. According to the official Claude prompt engineering documentation, the most effective prompts combine a clear role, context, and output format — every template below is built on that principle.

What you'll walk away with

Nine ready-to-use Claude prompt templates across three job roles, plus a clear pattern for adapting them to your own needs. First use takes about five minutes per template.

Before you start

• A Claude account — a free plan at claude.ai is enough to try all templates
• No installation needed — runs in any web browser
• To use the API, sign up separately at platform.claude.com

Quick glossary

• Prompt — The instruction you send to Claude. Think of it as a recipe card: the more clearly you describe the ingredients (context) and the method (instructions), the better the dish.
• Template — A reusable prompt skeleton with [bracketed placeholders] you swap out each time.
• XML tags — Markers like <context>…</context> that separate different sections of your prompt, helping Claude understand what's background information versus the actual task.
• Output format — The shape you want the answer in: bullet points, a table, "under 200 words," etc.

The principle behind every template

According to the official Claude prompt engineering documentation, a well-structured prompt includes three things: a role (who Claude should act as), context (situation, audience, constraints), and an output format (length, structure, language). Every template below follows this pattern — fill in the brackets and you're set.

💻 Developer Templates

1. Code Review Request

Use this when you want a quick, structured critique of code you've written.

You are a senior [language, e.g. Python] developer.
Please review the code below.

<context>
- Project type: [e.g. FastAPI backend / React frontend]
- What this code does: [one-line description]
- Areas I especially want feedback on: [e.g. error handling, performance, readability]
</context>

<code>
[paste your code here]
</code>

Please structure your feedback as follows:
1. Bugs or potential errors
2. Improvements (with reasoning)
3. Things done well

Use bullet points for each section, and include corrected code snippets where relevant.

2. Docstring & Module Documentation

Use this when you need comments or a README written quickly.

You are a technical documentation specialist.
Write a docstring and usage examples for the [language] function below.

<requirements>
- Audience: [e.g. junior developers on my team]
- Documentation style: [e.g. Google style / NumPy style / free-form]
- Language: English
</requirements>

<code>
[paste your function here]
</code>

Output format:
- Docstring (ready to insert directly below the function signature)
- Two usage examples
- Any important caveats or edge cases

3. Error Message Diagnosis

Use this when you hit an error and aren't sure what's causing it.

You are a [language] debugging specialist.
Analyze the error below and suggest how to fix it.

<error>
[paste the full error message here]
</error>

<context>
- Environment: [e.g. Python 3.11, macOS 14]
- What triggered the error: [brief description]
- Things I've already tried: [or "nothing yet"]
</context>

Please answer in this order:
1. Root cause (1–2 sentences)
2. How to fix it (step-by-step, with code)
3. How to prevent the same error in the future

📣 Marketer Templates

4. Social Media Post Draft

Use this to quickly generate post options for Instagram, LinkedIn, X, or similar platforms.

You are a social media marketer for a B2B SaaS brand.
Write [platform name] post drafts based on the brief below.

<brief>
- What to announce: [e.g. new feature launch, event, blog post]
- Core message in one sentence: [e.g. "You can now generate reports in 10 minutes"]
- Target audience: [e.g. startup marketers, SMB owners]
- Tone: [e.g. friendly and practical / professional and trustworthy]
</brief>

<constraints>
- Length: [e.g. under 280 characters]
- Hashtags: [e.g. 3]
- CTA: [e.g. "Start for free" with link placeholder]
</constraints>

Write three drafts, each using a different approach or angle.

5. Email Newsletter Section

Use this to draft a specific section of a regular newsletter quickly.

You are an email marketing copywriter.
Write a newsletter section based on the information below.

<context>
- Brand name: [brand name]
- Section topic: [e.g. this month's new feature]
- Key points to cover: [2–3 bullet points]
- Reader profile: [e.g. IT professionals, weekly subscribers]
</context>

<format>
- Subject line candidates: 3 options
- Body copy: 150–200 words
- CTA button text: 2 candidates
</format>

Write subject lines that encourage opens, and body copy that drives readers toward a single action.

6. Competitive Analysis Framework

Use this when you need a comparison structure for a positioning document or internal report.

You are a market analyst.
Suggest a framework and criteria for a competitive analysis based on the details below.

<context>
- Our product/service: [one-line description]
- Competitors to compare: [list names]
- Purpose: [e.g. internal strategy meeting / sales enablement]
- Our strengths to highlight: [e.g. price, speed, support]
</context>

Output format:
1. List of comparison criteria (up to 10, ordered by importance)
2. One-sentence explanation of what to evaluate for each criterion
3. Suggested data points worth researching

Note: I'll fill in the actual figures myself — please provide structure only.

📋 Planner / PM Templates

7. Product Requirements Document (PRD) Draft

Use this when you need to hand off a new feature to a development team. PRD stands for Product Requirements Document — a written spec that tells engineers what to build and why.

You are a product manager.
Write a PRD draft based on the feature details below.

<feature>
- Feature name: [e.g. Dark mode support]
- Background and problem: [what problem does this solve]
- Primary users: [persona or user type]
- Core usage scenario: [e.g. "User toggles dark mode in Settings, and…"]
</feature>

<constraints>
- Target timeline: [e.g. one 2-week sprint]
- Out of scope for this version: [what we're not doing now]
</constraints>

Please write a PRD draft with these sections:
1. Overview (2–3 sentences)
2. Goals and success metrics
3. Key features list (with priority)
4. Non-functional requirements (performance, accessibility, etc.)
5. Open questions (items needing further discussion)

8. Meeting Agenda & Minutes

Use this to prepare an agenda before a meeting, or to tidy up rough notes afterward.

You are a project manager.
Choose one task below and fill in the relevant section.

=== PRE-MEETING: Agenda ===
<meeting>
- Purpose: [e.g. Decide Q3 marketing strategy]
- Attendees: [by role, e.g. PM, marketer, designer]
- Available time: [e.g. 60 minutes]
- Must-decide items: [1–3 things]
</meeting>

Create a timed agenda and a preparation checklist for each item.

=== POST-MEETING: Minutes ===
<notes>
[paste your raw notes here — rough is fine]
</notes>

Organize into:
- Key decisions made
- Action items (owner · deadline)
- Topics to carry over to the next meeting

9. User Interview Question Guide

Use this to prepare questions for UX research or customer discovery interviews.

You are a UX researcher.
Create a user interview guide for the context below.

<context>
- Interview goal: [e.g. understand where users get stuck during onboarding]
- Participant profile: [e.g. users who signed up within the last 30 days]
- Key things to learn: [2–3 specific questions you want answered]
- Interview length: [e.g. 30 minutes]
</context>

Structure the guide as follows:
1. Icebreaker questions (2)
2. Core exploratory questions (5–7, open-ended)
3. Example follow-up probes (3)
4. Wrap-up questions (1–2)

Avoid yes/no questions and leading questions. Focus on drawing out real, specific experiences.

Troubleshooting: common sticking points

• The output feels too generic. The <context> block needs more detail. Add your target audience, brand tone, and specific constraints.
• The format isn't what I wanted. Add an explicit "Output format:" section at the end of your prompt describing the exact structure you need.
• The response is too long or too short. State a length constraint directly: "under 300 words" or "exactly five bullet points."
• The English feels off. Add a tone note: "conversational American English" or "formal business writing."
• Claude says it can't help. Try adding a short example inside an <example> tag — showing Claude a sample of what you want helps it match your style and intent.

Going further: three ways to get more from these templates

1. Build a personal context block. Write a short snippet with your brand name, target audience, and tone, then paste it at the top of every prompt. Consistency compounds over time.
2. Use the Claude Console prompting tools. According to the official documentation, the Claude Console includes a built-in prompt generator and prompt improver. If you use the API, paste a draft prompt there and ask for improvement suggestions.
3. Recycle good outputs as examples. When a response lands exactly right, save it. Adding "Please match the style and structure of this example:" to your next prompt is one of the fastest ways to maintain consistent quality.