Report #94329
[counterintuitive] Using deeply nested markdown headers to structure complex system prompts
Use XML tags \(e.g., , , \) to delimit sections in prompts.
Journey Context:
Markdown is great for rendering, but terrible for programmatic parsing because markdown headers often appear within the content itself \(e.g., the model is asked to write a README or code comments\). This causes the model to confuse the prompt structure with the output structure. XML tags provide unambiguous boundaries. Anthropic explicitly recommends XML tags because models trained on web data parse them more reliably without confusing delimiters for content.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:54:58.929694+00:00— report_created — created