Claude's XML Tag Superpower

Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, and expected outputs is one of the highest-leverage Claude-specific techniques.

32 min · Reviewed 2026

Why XML beats plain prose with Claude

Claude's training data included enormous amounts of XML-structured content. As a result, Claude treats XML tags as strong semantic signals — far more reliably than quotes, dashes, or 'the following article'. Tags also make your prompts self-documenting and easy to update programmatically.

A canonical tagged prompt

<role>
You are a senior editor at a reputable science magazine.
</role>

<task>
Review the draft below and suggest improvements for clarity and accuracy.
</task>

<style_guide>
- Prefer active voice.
- Define technical terms on first use.
- No clickbait.
- Maximum 600 words.
</style_guide>

<draft>
{USER_DRAFT}
</draft>

<examples>
<example>
<input>A quantum leap is small.</input>
<suggested_edit>Explain that 'quantum leap' in physics means the smallest possible change — counterintuitive given the everyday meaning.</suggested_edit>
</example>
</examples>

<output_format>
Provide your response as:
<summary>One-sentence overall assessment.</summary>
<edits>
  <edit location="paragraph 1">Suggestion.</edit>
  <edit location="paragraph 2">Suggestion.</edit>
</edits>
<next_step>One sentence telling the author what to do first.</next_step>
</output_format>A tagged prompt with role, task, rules, input, examples, and required output shape — all cleanly separated.

Tag naming conventions

Use descriptive, lowercase names: <research_notes>, not <rn>.
Be consistent within a prompt — don't switch between <doc> and <document>.
Nest when semantically meaningful: <examples><example>...</example></examples>.
Close every tag — Claude is forgiving but unclosed tags confuse it.

Output tags for parsing

If a downstream program will parse Claude's answer, require specific output tags. Then extract the content between them with a simple regex. This is more robust than JSON for long-form or mixed content.

Respond with exactly these tags, in this order:

<thinking>
Your reasoning, step by step.
</thinking>

<answer>
The final user-facing answer.
</answer>

<confidence>
A number from 1 (uncertain) to 5 (certain).
</confidence>Splitting internal reasoning from user-facing answer lets you hide 'thinking' from the end user while still logging it for analysis.

Hidden benefits

Without XML tags	With XML tags
User draft blurs into instructions.	Clear semantic boundaries.
Hard to update programmatically.	Trivial to template: replace <draft>{TEXT}</draft>.
Output formatting is fuzzy.	Downstream parsing is reliable.
Claude occasionally confuses roles.	Claude respects labeled sections.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prompting-xml-tags-creators

What is the core idea behind "Claude's XML Tag Superpower"?
1. Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, and expected outputs is one of the highest-leverage Claude-specific techniques.
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
Which term best describes a foundational idea in "Claude's XML Tag Superpower"?
1. semantic separation
2. XML tags
3. output parsing
4. prompt-design
A learner studying Claude's XML Tag Superpower would need to understand which concept?
1. XML tags
2. output parsing
3. semantic separation
4. prompt-design
Which of these is directly relevant to Claude's XML Tag Superpower?
1. XML tags
2. semantic separation
3. prompt-design
4. output parsing
Which of the following is a key point about Claude's XML Tag Superpower?
1. Use descriptive, lowercase names: <research_notes>, not <rn>.
2. Be consistent within a prompt — don't switch between <doc> and <document>.
3. Nest when semantically meaningful: <examples><example>...</example></examples>.
4. Close every tag — Claude is forgiving but unclosed tags confuse it.
Which of these does NOT belong in a discussion of Claude's XML Tag Superpower?
1. Use descriptive, lowercase names: <research_notes>, not <rn>.
2. prompt-design
3. Nest when semantically meaningful: <examples><example>...</example></examples>.
4. Be consistent within a prompt — don't switch between <doc> and <document>.
What is the key insight about "Works with JSON too" in the context of Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. You can mix — use XML to structure the input and ask for JSON output for the answer.
4. Propose a drop order under budget pressure.
What is the recommended tip about "Practitioner tip" in the context of Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Propose a drop order under budget pressure.
4. Treat every prompt as a spec: role → context → task → format. Review your first output as a draft, not a final.
Which statement accurately describes an aspect of Claude's XML Tag Superpower?
1. Claude's training data included enormous amounts of XML-structured content.
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
What does working with Claude's XML Tag Superpower typically involve?
1. prompt-design
2. If a downstream program will parse Claude's answer, require specific output tags. Then extract the content between them with a simple regex.
3. sample
4. Propose a drop order under budget pressure.
Which best describes the scope of "Claude's XML Tag Superpower"?
1. It is unrelated to prompting workflows
2. It applies only to the opposite beginner tier
3. It focuses on Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, an
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Propose a drop order under budget pressure.
4. A canonical tagged prompt
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. Tag naming conventions
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. Output tags for parsing
3. sample
4. Propose a drop order under budget pressure.
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Hidden benefits
4. Propose a drop order under budget pressure.

← Back to interactive lesson

Tendril · Creators · Prompting

Claude's XML Tag Superpower

Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, and expected outputs is one of the highest-leverage Claude-specific techniques.

32 min · Reviewed 2026

Why XML beats plain prose with Claude

A canonical tagged prompt

<role>
You are a senior editor at a reputable science magazine.
</role>

<task>
Review the draft below and suggest improvements for clarity and accuracy.
</task>

<style_guide>
- Prefer active voice.
- Define technical terms on first use.
- No clickbait.
- Maximum 600 words.
</style_guide>

<draft>
{USER_DRAFT}
</draft>

<examples>
<example>
<input>A quantum leap is small.</input>
<suggested_edit>Explain that 'quantum leap' in physics means the smallest possible change — counterintuitive given the everyday meaning.</suggested_edit>
</example>
</examples>

<output_format>
Provide your response as:
<summary>One-sentence overall assessment.</summary>
<edits>
  <edit location="paragraph 1">Suggestion.</edit>
  <edit location="paragraph 2">Suggestion.</edit>
</edits>
<next_step>One sentence telling the author what to do first.</next_step>
</output_format>A tagged prompt with role, task, rules, input, examples, and required output shape — all cleanly separated.

Tag naming conventions

Use descriptive, lowercase names: <research_notes>, not <rn>.
Be consistent within a prompt — don't switch between <doc> and <document>.
Nest when semantically meaningful: <examples><example>...</example></examples>.
Close every tag — Claude is forgiving but unclosed tags confuse it.

Output tags for parsing

Respond with exactly these tags, in this order:

<thinking>
Your reasoning, step by step.
</thinking>

<answer>
The final user-facing answer.
</answer>

<confidence>
A number from 1 (uncertain) to 5 (certain).
</confidence>Splitting internal reasoning from user-facing answer lets you hide 'thinking' from the end user while still logging it for analysis.

Hidden benefits

Without XML tags	With XML tags
User draft blurs into instructions.	Clear semantic boundaries.
Hard to update programmatically.	Trivial to template: replace <draft>{TEXT}</draft>.
Output formatting is fuzzy.	Downstream parsing is reliable.
Claude occasionally confuses roles.	Claude respects labeled sections.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-prompting-xml-tags-creators

What is the core idea behind "Claude's XML Tag Superpower"?
1. Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, and expected outputs is one of the highest-leverage Claude-specific techniques.
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
Which term best describes a foundational idea in "Claude's XML Tag Superpower"?
1. semantic separation
2. XML tags
3. output parsing
4. prompt-design
A learner studying Claude's XML Tag Superpower would need to understand which concept?
1. XML tags
2. output parsing
3. semantic separation
4. prompt-design
Which of these is directly relevant to Claude's XML Tag Superpower?
1. XML tags
2. semantic separation
3. prompt-design
4. output parsing
Which of the following is a key point about Claude's XML Tag Superpower?
1. Use descriptive, lowercase names: <research_notes>, not <rn>.
2. Be consistent within a prompt — don't switch between <doc> and <document>.
3. Nest when semantically meaningful: <examples><example>...</example></examples>.
4. Close every tag — Claude is forgiving but unclosed tags confuse it.
Which of these does NOT belong in a discussion of Claude's XML Tag Superpower?
1. Use descriptive, lowercase names: <research_notes>, not <rn>.
2. prompt-design
3. Nest when semantically meaningful: <examples><example>...</example></examples>.
4. Be consistent within a prompt — don't switch between <doc> and <document>.
What is the key insight about "Works with JSON too" in the context of Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. You can mix — use XML to structure the input and ask for JSON output for the answer.
4. Propose a drop order under budget pressure.
What is the recommended tip about "Practitioner tip" in the context of Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Propose a drop order under budget pressure.
4. Treat every prompt as a spec: role → context → task → format. Review your first output as a draft, not a final.
Which statement accurately describes an aspect of Claude's XML Tag Superpower?
1. Claude's training data included enormous amounts of XML-structured content.
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
What does working with Claude's XML Tag Superpower typically involve?
1. prompt-design
2. If a downstream program will parse Claude's answer, require specific output tags. Then extract the content between them with a simple regex.
3. sample
4. Propose a drop order under budget pressure.
Which best describes the scope of "Claude's XML Tag Superpower"?
1. It is unrelated to prompting workflows
2. It applies only to the opposite beginner tier
3. It focuses on Claude was trained heavily with XML-tagged examples. Using tags to separate inputs, instructions, an
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Propose a drop order under budget pressure.
4. A canonical tagged prompt
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. Tag naming conventions
2. prompt-design
3. sample
4. Propose a drop order under budget pressure.
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. Output tags for parsing
3. sample
4. Propose a drop order under budget pressure.
Which section heading best belongs in a lesson about Claude's XML Tag Superpower?
1. prompt-design
2. sample
3. Hidden benefits
4. Propose a drop order under budget pressure.

← Back to interactive lesson