Claude Prompt Generator

Describe your goal in plain English. PromptVibe writes a Claude prompt structured the way Anthropic recommends — each part in its own XML tag, long material first, instructions spelled out. Free, no account needed.

Write my Claude prompt — free →Compare AI models

A Claude prompt generator turns a plain-language goal into a prompt structured the way Anthropic's documentation recommends: clear, explicit instructions with the reason behind them, long documents placed above the question, each part wrapped in its own XML tag, and a few examples of the output you want. PromptVibe writes that structure for you, free.

How Claude prompts differ

  • XML tags keep the parts apart: Anthropic's guidance is that XML tags help Claude parse prompts that mix instructions, context, examples and inputs, and that wrapping each in its own tag — such as <instructions>, <context> and <input> — reduces misinterpretation. When Claude is the target model, PromptVibe writes the prompt this way.
  • Long material goes first, the question last: Anthropic recommends placing long documents and inputs near the top of the prompt, above the query, instructions and examples. Pasting a contract under your question is the most common way long-document prompts go wrong.
  • Current Claude models do what you say, not what you meant: Anthropic notes that its latest models are trained for precise instruction following: ask "can you suggest some changes" and you may get suggestions rather than edits. If you want more than the literal request — extra features, a thorough review, the edit itself — say so explicitly.
  • The reason behind a rule changes the result: Explaining why an instruction matters helps Claude deliver a more targeted response. "Under 80 words, because it is read on a phone" generalizes better than "under 80 words" alone.

Techniques that work

  • Give Claude a role in one sentence. Anthropic's documentation says setting a role focuses Claude's behavior and tone, and that even a single sentence makes a difference. Name the role and who the output is for.
  • Show three to five examples, tagged. Examples are one of the most reliable ways to steer format, tone and structure. Anthropic suggests 3–5 varied examples wrapped in <example> tags (inside <examples> when there are several) so they are not mistaken for instructions.
  • Say what to do instead of what not to do. "Write in flowing prose paragraphs" works better than "don't use markdown". Describe the output you want, and match the style of your prompt to it.
  • Ground long-document answers in quotes. For a long document, ask Claude to copy the relevant passages into <quotes> tags first, then answer using only those. It keeps the answer tied to the text and makes it easy to check.
  • Developers: don't rely on prefilled replies. Through the API, prefilling the assistant's reply on the last turn is not supported starting with Claude 4.6 models and returns an error. Use a direct instruction, XML-tagged output or structured outputs instead.

Example Claude prompts

Contract review — long document first, quotes before analysis

<contract>
[Paste the full contract text here]
</contract>

<instructions>
You are reviewing this contract for a small agency that is the service provider.
1. Copy the clauses about payment terms, liability and termination into <quotes> tags, word for word.
2. Using only those quotes, rate each clause Low / Medium / High risk for the agency, with one sentence on why.
3. End with the three points the agency should negotiate, in plain English.
If one of these clauses is missing, say so instead of guessing.
</instructions>

Customer support reply — role + tagged example

<role>
You are the support lead at a small software company. Customers read replies on their phones, so keep them short and warm.
</role>

<customer_email>
[Paste the customer's email here]
</customer_email>

<task>
Reply to the email above: acknowledge the problem in one sentence, give the fix as numbered steps, and offer a direct reply if it does not work. Under 120 words.
</task>

<examples>
<example>
Sorry the export failed twice — that is frustrating. Here is the fix:
1. Open Settings → Data.
2. Choose "Export as CSV" instead of XLSX.
If that does not work, reply here and I will run the export for you.
</example>
</examples>

Code change — explicit action + output format

<context>
Next.js 14 app in TypeScript. On slow connections the checkout button can submit twice.
</context>

<task>
Change the CheckoutButton component so it cannot submit twice: disable it while the request is pending and re-enable it if the request fails. Make the change — do not just describe it. Keep the existing props and styling.
</task>

<output_format>
The full updated component in one code block, then two sentences on what changed.
</output_format>

Test it before you trust it

A prompt that reads well is not the same as a prompt that works. The Compare AI Lab runs the same prompt through up to three models side by side so you can see which one actually handles your task, and the A/B tester scores two versions of a prompt against criteria you choose. Free members get a comparison every day.

Limitations

  • PromptVibe is independent and not affiliated with or endorsed by Anthropic.
  • The example prompts on this page are illustrative. They show structure; they were not benchmarked.
  • A well-structured prompt improves the odds, not the outcome. Test it on your real task before relying on it.
  • Claude behaves differently across model versions and between the Claude apps and the API. Prefill and similar API details do not apply in the apps.

Frequently asked questions

Is this an official Anthropic or Claude tool?

No. PromptVibe is an independent tool with no affiliation with Anthropic. It generates structured prompts you can use with Claude, but it is not created or endorsed by Anthropic.

Should I use XML tags in Claude prompts?

For anything longer than a quick question, yes. Anthropic's documentation recommends XML tags when a prompt mixes instructions, context, examples and inputs. Use clear, consistent names such as <instructions>, <context> and <input>, and refer to them by name in your instructions.

Where should I put a long document in a Claude prompt?

At the top, above your question and instructions. Anthropic recommends this placement for long inputs. For long documents, also ask Claude to quote the relevant passages first and answer from those quotes.

Do I still need to tell Claude to "think step by step"?

The phrase on its own adds little with current models, which can reason before answering. A stronger instruction is to state the criteria a good answer must meet and ask Claude to check its answer against them before it finishes.

Do the PromptVibe frameworks work with Claude?

Yes. All seven — Standard, ROLE, TAG, COAST, RACE, RISE and APE — work with Claude. When Claude is the target model, PromptVibe writes the result with XML tags so the role, task and constraints stay separate.

Sources

The Claude-specific guidance above follows Anthropic's own documentation, last checked on October 19, 2026. Anthropic updates it as models change, so check the source if something here stops matching what you see.

Related tools

Write my Claude prompt — free →