This is a list of tricks/hints to smoothly work with Claude.
Never copy from the terminal. Konsole copies what is displayed, so it inserts a hard line break at every visual wrap—against the one-paragraph-one-line rule—and drags in the bullets and box-drawing characters. The wiki wants the markdown Claude emitted, not the text on screen; those differ, and only Claude still has the first one.
Instead, instruct it to wiki this to <page>. Claude does the edit through the API: it wraps the exchange in {{AI}}, fetches the current revision, shows the diff, and posts with basetimestamp. Nothing passes through a copy step, so nothing can be mangled. This is the default route.
Ask for the raw markdown on the clipboard, then paste it into an {{AI}} call. Raw markdown, not wikitext — Module:AI converts markdown itself, and hand-converting silently loses things.
{{AI|AI=Claude|v=Opus 5|q=my prompt, verbatim|a=
the markdown answer, exactly as emitted
}}
AI=Claude gives the logo and the tint, so it reads at a glance as a Claude output rather than as my own prose. Second person (your machine) is correct inside the box: it is a quoted exchange. The human defaults to Fabrice.
A literal pipe, i.g., | anywhere in the answer breaks the a= parameter: save the reply to a subpage and use src= instead, which is read verbatim so pipes, tables, braces and = are all safe.
Don't wrap prose in <syntaxhighlight>. It renders white-space: pre and never wraps, so each one-line paragraph becomes a single ~500-character line, causing huge sideways scrolling. It also shows **bold** and fences as literal characters, leaving the code un-highlighted.
The route above assumes Claude Code, which still has the Markdown it emitted. Reading an answer in the web app I have only the rendered page, and selecting a piece of it with the mouse gives a poor copy: the structure is flattened, and every formula falls apart into loose glyphs, sometimes doubled, because that is what the plain-text flavour of the clipboard holds.
It is only that flavour that is impoverished. The same copy also sits on the clipboard as text/html, and KaTeX keeps the $\mathrm{\TeX}$ it was given inside the MathML annotation of each formula, so the LaTeX is already there—it is the paste that throws it away. html2md reads the other flavour and hands back the Markdown, maths included—and where the page is rendered by MathJax, which keeps no LaTeX at all, it rebuilds the LaTeX from the MathML.
Copy, paste. There is no step in between: a watcher started at login converts every copy as it arrives, adding the Markdown as the plain-text flavour and leaving the original HTML in place for anything that wants formatting. What lands in the edit box is Markdown, ready for an {{AI}} call exactly as above, with $...$ and $$...$$ that SimpleMathJax renders. Any table in it can be made into a real wikitable by passing the result through mdtable2wiki.