HTML is the new Markdown: How Anthropic engineers are building with Claude Code | Thariq Shihipar
Episode
35 min
Read time
2 min
Topics
Fundraising & VC, Leadership, Design & UX
AI-Generated Summary
Key Takeaways
- ✓HTML over Markdown for specs: When Claude generates plans as HTML files instead of markdown, builders actually read them. Thousand-line markdown documents go unread and unedited, while HTML renders scrollable, visual, diagram-rich plans that pull readers in and prompt genuine engagement — directly raising the quality of what the agent builds next.
- ✓Compute allocator as the new PM role: Running Claude for eight hours costs roughly $500 in compute. The core skill of product management has shifted to deciding what is worth spending that compute on. Spec and planning phases are where those allocation decisions get made, making upfront clarity about goals more valuable than ever.
- ✓Micro-apps for editing specific plan sections: When one section of an HTML plan needs revision, ask Claude to build a throwaway custom UI specifically for editing that module — interactive fields, toggles, copy-out buttons — then paste the refined output back into the main plan. This targets precision edits without re-litigating the entire document in terminal.
- ✓Living design system as design.html: Store the design system as an HTML file rather than a markdown document. The file encodes colors, typography, spacing, and core components in a visually rendered, compressed format that Claude can reference directly in any new project folder, replacing design.md and eliminating ambiguity about component styling.
- ✓Prompt structure for HTML plans: Keep prompts short but include two specific anchors — the content type you need (code excerpts, mock-ups, logic diagrams) and an open-ended trust signal ("whatever is needed for maximum context"). Over-constraining with role prompts like "you are an expert planner" limits output quality more than under-specifying does.
What It Covers
Thariq Shihipar, an Anthropic engineer on the Claude Code team, demonstrates how replacing markdown with HTML files transforms the planning and specification process — producing richer, more readable artifacts that keep builders engaged with agent outputs and ultimately improve the quality of what gets built.
Key Questions Answered
- •HTML over Markdown for specs: When Claude generates plans as HTML files instead of markdown, builders actually read them. Thousand-line markdown documents go unread and unedited, while HTML renders scrollable, visual, diagram-rich plans that pull readers in and prompt genuine engagement — directly raising the quality of what the agent builds next.
- •Compute allocator as the new PM role: Running Claude for eight hours costs roughly $500 in compute. The core skill of product management has shifted to deciding what is worth spending that compute on. Spec and planning phases are where those allocation decisions get made, making upfront clarity about goals more valuable than ever.
- •Micro-apps for editing specific plan sections: When one section of an HTML plan needs revision, ask Claude to build a throwaway custom UI specifically for editing that module — interactive fields, toggles, copy-out buttons — then paste the refined output back into the main plan. This targets precision edits without re-litigating the entire document in terminal.
- •Living design system as design.html: Store the design system as an HTML file rather than a markdown document. The file encodes colors, typography, spacing, and core components in a visually rendered, compressed format that Claude can reference directly in any new project folder, replacing design.md and eliminating ambiguity about component styling.
- •Prompt structure for HTML plans: Keep prompts short but include two specific anchors — the content type you need (code excerpts, mock-ups, logic diagrams) and an open-ended trust signal ("whatever is needed for maximum context"). Over-constraining with role prompts like "you are an expert planner" limits output quality more than under-specifying does.
Notable Moment
Shihipar revealed he sends his manager a weekly status update generated entirely by Claude reading his Slack messages, formatted as an HTML document. The result is that his manager actually reads it — something that rarely happened with plain-text updates — with minimal time investment on his part.
Episode Transcript
Markdown became a really popular way of interacting with agents, but the plans are so long. I honestly have stopped reading them. And this is honestly a mistake. I think that you still need to be really in the loop. Plans matter. PRDs matter. Spec matters. When you say, okay, Claude can run for eight hours, what you're really saying is Claude can spend $500. All of us are becoming these compute allocators now. Right? And so you have to decide what is worthwhile spending the compute on. People ask me all the time, Claire, you said product management is dead. What's next? And I'm gonna say, you're a compute allocator, babe. That's the job now. HTML is a lot easier to read, and so it's just a richer communication medium between you and Claude. Instead of saying, here's a markdown document, it was like, what's the best way to convey this information? So you can actually engage with it and pick something. This is the plan. It's purely an HTML. This is something that I will actually read. This is not even personal software. It's like micro software, on top of micro software. Welcome back to How I AI. I'm Claire Vaux, product leader and AI obsessive here on a mission to help you build better with these new tools. Recently, I was able to attend Code with Claude, Anproppet's first developer conference. And as part of that, I got to spend a little time with Tarek, who works on Claude code and taught me something that has blown my mind ever since I heard it. HTML is the new markdown. He's gonna show us how to use cloud code to generate rich artifacts that both you and the agents can enjoy working on. Let's get to it. This episode is brought to you by Soligo. Every company today wants AI to improve how work gets done. The fastest way is building it directly into everyday business processes, automating employee onboarding, keeping customer data accurate, managing orders and inventory, or resolving finance and operations issues. When AI lives inside the flow of work, it can update records, trigger approvals, route work, and kick off the next step across systems. That's how teams operationalize AI and deliver measurable results. Seligo makes this possible. And now with Seligo Aura, it's never been easier. Seligo Aura gives you access to the entire platform through natural language, connecting your systems and turning intent into action. All of it under your control. Companies like Databricks, PayPal, and Olipop rely on Celigo to run critical business operations at scale. Ready to operationalize AI? Visit celigo.com/howiai. That's celigo.com/howiai. Welcome to howiai. Thanks for having me. I am so excited to be here at Code with Claude in San Francisco. There's a lot of exciting things that were announced, and we'll get to that in a little bit. But you told me something I was not expecting to hear today, which is you heard it here first. …
Get the full transcript (7,203 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 32-minute episode.
Get How I AI summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from How I AI
I tested Grok Bot, Grok 4.6, and Cursor Origin - here’s my honest take
Aug 18 · 27 min
Lenny's Podcast
Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)
Jun 21
More from How I AI
How a solo founder used Codex and ChatGPT to launch a fashion brand without engineers | Yana Welinder
Aug 17 · 32 min
The Daily (NYT)
Can A.I. Already Do Your Job?
Feb 18
More from How I AI
We summarize every new episode. Want them in your inbox?
I tested Grok Bot, Grok 4.6, and Cursor Origin - here’s my honest take
How a solo founder used Codex and ChatGPT to launch a fashion brand without engineers | Yana Welinder
Claude Code for normal people: skills, voice mode, and how to collaborate with AI
Build an AI code review bot in 30 minutes with Vercel Eve
ChatGPT Codex Voice + browser + Sites: an expert’s AI workflow | Nick Baumann (OpenAI)
Similar Episodes
Related episodes from other podcasts
Lenny's Podcast
Jun 21
Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)
The Daily (NYT)
Feb 18
Can A.I. Already Do Your Job?
Lenny's Podcast
Jul 26
Anthropic’s first technical PM on token maxing, the jagged edge, and living in the future | Dianne Penn
The AI Breakdown
Jun 24
5 Ways Claude Tag Could Change How You Use AI
Lenny's Podcast
Apr 23
How Anthropic’s product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code)
Explore Related Topics
This podcast is featured in Best AI Podcasts (2026) — ranked and reviewed with AI summaries.
You're clearly into How I AI.
Every Monday, we deliver AI summaries of the latest episodes from How I AI and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime