Quartz 5

Using Claude Code: The Unreasonable Effectiveness of HTML

Properties1
tagsclaude-code, agentic-workflow, llm

2 min read

Summary

A Claude Code team member makes the case that HTML is a superior output format to Markdown for AI-generated documents. HTML’s ability to render tables, SVG, CSS, interactive JavaScript, and spatial layouts enables far richer communication of complex information than Markdown’s limited formatting. The author has largely abandoned Markdown entirely for planning, code review, design prototyping, and reporting use cases.

Claude Code 團隊成員主張，HTML 比 Markdown 更適合作為 AI 生成文件的輸出格式。HTML 支援表格、SVG、CSS、JavaScript 互動及空間排版，能傳遞 Markdown 無法呈現的豐富資訊。作者在規劃、程式審查、設計原型與報告等場景已幾乎完全放棄 Markdown。

Key Points

  • Markdown caps practical readability at ~100 lines; HTML documents with tabs, links, and illustrations scale much further
  • HTML enables two-way interaction (sliders, knobs, “copy as JSON” buttons) that lets users modify parameters and paste results back into Claude Code
  • Claude Code’s data ingestion strength — filesystem, MCPs, git history — is best leveraged when the output format can represent all that context richly
  • HTML is slower to generate (2-4x) and produces noisy diffs, which are real trade-offs
  • The recommendation is to prompt ad-hoc (“make an HTML artifact”) rather than building a dedicated /html skill

Insights

The key realization is that AI agents have already removed one of Markdown’s main advantages (human editability) while HTML removes Markdown’s main disadvantage (limited expressiveness). When you are no longer the primary editor of the document, the format optimum shifts dramatically toward richness over parsimony.

Connections

Raw Excerpt

“I’m also increasingly not editing these files myself, but using them as specs, reference files, brainstorming outputs, etc. When I do make edits, I’m usually prompting Claude to edit them, which removes one of markdown’s largest benefits.”

Graph View

Backlinks