Use case · R&D · Claude

XML tool built with Claude

[FILL: one-line summary, e.g. "A Claude-generated converter that turns supplier CSV exports into our internal XML format, saving R&D ~3 hours per week."]

By [FILL: Author name, role, department] · Contact: [FILL: email or Teams handle]

Editor note (remove before publish): Every yellow [FILL: …] on this page must be replaced with real content from the author. Walk through this template with the author in a 15-min call. Capture the prompts verbatim.

The problem

[FILL: 2–4 sentences describing what was painful before. What were people doing manually? How long did it take? What broke?]

How it was built

[FILL: 3–5 sentences describing the build process. Was it one conversation with Claude, or iterative? Is the prompt re-used or one-off? What tooling around it?]

The prompts

The prompts are copy-pasteable — click "Copy" on each block.

[FILL: Prompt 1 — the main / system prompt, verbatim]

[FILL: Prompt 2 — if there's a follow-up or refinement prompt; otherwise delete this block]

What it produces

[FILL: 1–2 sentences describing the output. Format, where it lands, who uses it downstream.]

[FILL: drop images/xml-tool-output.png — screenshot of the actual output, redact internal data]

Reuse it

The prompts above are copy-pasteable. To adapt this for your own input:

[FILL: First adaptation step — e.g., "Replace [field name] with your equivalent."]
[FILL: Second adaptation step.]
[FILL: Third adaptation step.]

Need help adapting? Contact the author above, or ask any ambassador.

Caveats — what didn't work, what to watch out for

[FILL: First caveat — e.g., "Claude occasionally invents element names if the input format isn't strict; always validate the XML before downstream use."]
[FILL: Second caveat]

Data classification: [FILL: confirm with author whether prompts/inputs contain internal Qvantum data. If unsure, flag with Petter/IT before publishing.]

Submitted [FILL: date] · Last reviewed 2026-05-15 · Tags: R&D · Claude · XML