As Claude Code takes on bigger chunks of planning, design, and review, the format of its output starts to matter more than the prompt. A new piece from Thariq Shihipar makes the case for HTML over Markdown.

Two ideas worth sitting with: HTML gives Claude a richer canvas (SVG diagrams, rendered diffs, interactive sliders, export buttons), and it raises the odds that you and your team actually read what it produced. He also frames HTML artifacts as a way to stay in the loop with Claude's choices instead of rubber-stamping them.

I think I’ll start trying this in certain circumstances, but their is more token burn so not going to use in all cases.