Why This Claude Code Engineer Uses HTML Files as AI Specs | Thariq Shihipar (Anthropic)

Why It Matters

Using HTML for AI specs transforms how teams collaborate with large language models, boosting readability, reducing costly compute waste, and reshaping product management toward more visual, cost‑conscious workflows.

Key Takeaways

• HTML replaces markdown for richer AI spec communication.
• Developers become compute allocators, managing cost of AI runs.
• Visual HTML outputs improve readability and decision‑making significantly.
• Simple prompts let Claude generate full spec, mockups, code.
• Integrated HTML specs combine PRDs, tech specs, and demos.

Summary

The video spotlights Anthropic’s Claude Code engineer Thariq Shihipar, who argues that HTML is supplanting markdown as the preferred format for AI‑generated specifications. By embedding rich visual elements, HTML files become a more engaging medium for both humans and large language models, streamlining the planning and implementation phases of AI‑driven projects.

Shihipar explains that as model outputs grow longer, traditional markdown plans become unwieldy, prompting a shift toward HTML’s scrollable, interactive layout. He emphasizes that engineers are now “compute allocators,” balancing cloud runtime costs against project value, and that clear, visual specs help them make smarter spending decisions. Simple, open‑ended prompts enable Claude to produce comprehensive plans that include mockups, code snippets, and contextual excerpts.

Key moments include the claim “HTML is the new markdown,” a live demo where Claude brainstorms eight product ideas in an HTML file, and the generation of a full implementation plan complete with mood boards and sample scripts. Shihipar also notes that HTML allows developers to merge PRDs, technical specs, and demo assets into a single, navigable document, something markdown struggles to achieve.

The shift signals a broader evolution in product management: specifications will become more visual, interactive, and cost‑aware, reducing the friction between AI output and human oversight. Organizations that adopt HTML‑based AI specs can expect faster iteration cycles, clearer stakeholder communication, and tighter control over compute expenditures.

Original Description

Thariq Shihipar is an engineer at Anthropic working on the Claude Code team. He’s spent the past several months experimenting with HTML as a replacement for Markdown in planning and implementation workflows, discovering that richer visual formats lead to better human engagement—and, ultimately, better products. In this episode, filmed at Anthropic’s Code with Claude event in San Francisco, Thariq demonstrates how to use HTML artifacts to create interactive plans, build throwaway UIs for specific problems, and maintain living design systems that travel with your codebase.

What you’ll learn:

1. Why HTML has replaced Markdown as the ideal format for AI agent communication and planning

2. How to brainstorm in HTML to get visual mockups and interactive demos instead of text lists

3. The technique for building throwaway micro-UIs to edit specific parts of your plan

4. How to create a living design system in HTML that lives in your repo and travels with every project

5. Why “complexity has to earn its keep” and how HTML helps you stay in the loop without over-constraining Claude

6. The prompting technique that gives Claude flexibility while ensuring that you get what you need

7. Why 99% of your AI-generated tokens should go to planning, interfaces, and communication—not production code

Brought to you by:

Celigo—Intelligent automation built for AI: https://celigo.com/howIAI

Persona—Trusted identity verification for any use case: https://withpersona.com/lp/howiai

In this episode, we cover:

(00:00) Introduction

(02:39) HTML as the new Markdown

(04:30) The compute allocator mindset

(05:51) How HTML makes specs more engaging

(06:48) Demo: Brainstorming in HTML with Claude Code

(09:24) From brainstorm to full implementation plan

(11:20) Prompting philosophy: Trust Claude but give it constraints

(13:50) The future of PRDs and tech specs

(18:16) Making HTML specs editable

(20:23) The abundance mindset

(24:17) Just-in-time documentation and throwaway software

(25:39) Using plans as artifacts for implementation

(26:39) Demo: Living design systems in HTML

(30:16) Adding comments and annotations to HTML plans

(31:42) Recap: The HTML workflow

(32:21) Lightning round and final thoughts

Blog

How I AI: Thariq Shihipar on Replacing Markdown with HTML for AI-Powered Development: https://www.chatprd.ai/how-i-ai/claude-code-anthropic-thariq-shihipar-on-replacing-markdown-with-html

Detailed workflow walkthroughs:

↳ Generate a Living HTML Design System with AI for UI Consistency: https://www.chatprd.ai/how-i-ai/workflows/generate-a-living-html-design-system-with-ai-for-ui-consistency

↳ Build Disposable Micro-Apps with AI to Edit Complex Plans: https://www.chatprd.ai/how-i-ai/workflows/build-disposable-micro-apps-with-ai-to-edit-complex-plans

↳ Create Interactive HTML Project Plans with AI for Better Visualization: https://www.chatprd.ai/how-i-ai/workflows/create-interactive-html-project-plans-with-ai-for-better-visualization

Tools referenced:

• Claude Code: https://claude.ai/code

• Claude Design: https://claude.ai/design

• AWS: https://aws.amazon.com/

• Figma: https://www.figma.com/

• GitHub: https://github.com/

Other references:

• Anthropic Code with Claude event: https://claude.com/code-with-claude

• SpaceX partnership announcement: https://www.anthropic.com/news/higher-limits-spacex

• Jevons paradox: https://en.wikipedia.org/wiki/Jevons_paradox

Where to find Thariq Shihipar:

Website: https://www.thariq.io/

LinkedIn: https://www.linkedin.com/in/thariqshihipar/

X: https://x.com/trq212

GitHub: https://github.com/ThariqS

Where to find Claire Vo:

ChatPRD: https://www.chatprd.ai/

Website: https://clairevo.com/

LinkedIn: https://www.linkedin.com/in/clairevo/

X: https://x.com/clairevo

_Production and marketing by https://penname.co/._

_For inquiries about sponsoring the podcast, email [e-mail]._