# HTML Replaces Markdown for AI Agent Workflows

**Podcast:** How I AI
**Published:** 2026-05-18

## 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 bucks.
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?
I'm going to 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 in 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 Clara 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, Anthropics' first developer conference.
And as part of that, I got to spend a little time with Tharik, 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 going to show us how to use Claude 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 Celigo.
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.
Soligo makes this possible.
And now, with Soligo Aura, it's never been easier.
Soligo 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 Soligo to run critical business operations at scale.
Ready to operationalize AI?
Visit soligo.com slash howiai.
That's C-E-L-I-G-O dot com slash howiai.
Welcome to How I AI.
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.
HTML is the new Markdown.
Tell us more.
I mean, I think Markdown became a really popular way of interacting with agents, especially like, you know, Opus 4 and Claude 3.5, where, you know, they have a plan.
And the plan is like.
how to do this feature and maybe it's like 50 lines of code and you can edit it right like i think back then you were still like reading all the outputs and editing the markdown and making it right but you know as the agents have gotten longer and longer running when you have opus 4.5 and 4.7 they're running for like an hour or something and the plans are so long i honestly have stopped reading them and this was honestly a mistake like i think that you still need to be really in the loop you really need to understand what the agents are doing But like a thousand line markdown file, you know, I don't even edit them anymore.
I just ask Claude to edit them instead.
And so I think one of the things that I've been seeing emergently in the Claude code team is that like they that we're using HTML files instead.
And so HTML is like the models are still very good at it.
They have a lot of more context now.
So you can spend the more extra tokens.
And they like it's a lot easier to read.
Like they can have a lot more information.
They're a lot more scrollable.
When you're talking about implementation, like, you know, sometimes you see Claude make these like little ASCII markdown things where you're like, oh, like, here's a little, you know, little mockup and it's trying really hard.
In HTML, it doesn't need to try nearly as hard, right?
It can actually draw like things that you can look at.
And so it's just a richer communication medium between you and Claude.
And before we go further into HTML specifically, I do have to pause because I do have a vested interest in this.
Sure.
Which is you are saying for the people who are not listening, listen up.
Yes.
Plans matter.
PRDs matter.
Spec matters.
Even as these models get more intelligent, you still feel like that's a really important part of the process.
Oh, 100 percent.
Yeah.
I think that, you know, everyone has different views on how it'll go.
But I think that this will just forever be the thing, because when you say, OK, Claude can run for eight hours.
What you're really saying is Claude can spend like 500 bucks.
You know what I mean?
And so if you're spending 500 bucks or like I think all of us are becoming these compute allocators now, right?
And so you have to decide like what is worthwhile spending the compute on.
And I think that happens in the spec and planning phase, right?
You have to really understand like what do you want?
And sometimes you don't know.
Sometimes you have to like pull it out of yourself by chatting with Claude.
Sometimes you have like unknown unknowns you need to figure out.
But yeah, I think this is like the whole thing now is just like really getting in sync with Cloud about what's building.
I love what you said because people ask me all the time, Claire, you said product management is dead.
What's next?
I'm going to say you're a compute allocator, babe.
Like that's the job now.
You're still doing the same thing, though.
You're writing documents to decide whether or not something else should do work in the shape of that work.
OK, so you've convinced me HTML is the future.
And I like how you said this.
It's not that.
It is necessarily harder or easier for the agents to read.
They're very smart.
They can read all sorts of code.
But in fact, what you're finding is that HTML makes it easier for you to engage with the content, which then up levels the quality overall because you're not your eyes aren't crossing looking at a bunch of raw markdown being like, whatever, it's probably good.
Instead, you're actually getting pulled into the spec or the document or the plan.
And then.
interacting it with a way that upgrades the quality and then you can ultimately build something better.
Yeah, that's right.
Okay, so you're building something with the agent so the agent can manage you.
You know, I'm not sure if manage me is the right word exactly, but, you know, I just, I care a lot about being in sync with the agent.
This is sort of like the features that I built in Cloud Code have been like that, you know, like how can I get to know you better?
So, yeah.
Okay, great.
Well.
We have we have Claude code up.
So let's walk through how that how that works.
Yeah.
So I did like a little bit before we started.
And so I like to talk with Claude just as a human, you know, and like I always start with brainstorming.
It's so much easier to brainstorm once you like, you know, once you have a partner.
So I was literally like, look, I'm on a Clairvro podcast.
I want to do a demo, you know, and can you brainstorm some ideas in an HTML file, right?
And this is literally the prompt I gave it, right?
Like there's not, it's not complicated.
And so here you can see the eight visual demos that it made for me.
And it has these little mock-ups as well, right?
So like PRD to working prototype, right?
Like it searched you up, right?
You saw that with a web search, right?
Whiteboard sketch to working UI, which I thought was really cool.
This is such a cute little thing.
It is extremely cute.
And what's really funny is just this morning, a ChatPurity user messaged me.
And they're like, I love the mockups in ChatPurity.
And I'm like, what in the world?
What are you talking about?
Because I have something very similar to this in code review right now and haven't shipped it.
And I'm like, did I act a clawed accidentally do this?
And it was that cute little app.
below ASCII, you know, wireframe.
So this is definitely the dream.
Yes.
But not even, but now you're telling me I'm going to build it.
So it's giving you basically, instead of saying, here's a markdown document of kind of like what you should talk to Claire about, some descriptions of things you could do.
Instead, it was like, what's the best way to convey this information?
So you can actually engage with it and pick something.
And it used HTML to make this.
visual guide of a potential agenda or a set of demos and you just get like a much richer expression.
Yeah, exactly.
Like I think like another like for brainstorming, one of my like sort of rules of thumb is that I'm not going to read a longer output than the screen on Cloud Code, you know?
So like if I if you gave me eight ideas, I'm just not going to see all of them.
But with HTML, I'm definitely I scroll through all of these, you know, and yeah, the.
The diagrams just make it so much more evocative for me to, like, sort of understand what's happening, right?
The slash command starter pack, five code of feature flag dashboard.
Yeah, PRD diet.
And the one I ended up liking the most was the CSV to interactive dashboards.
We love a dashboard.
I used to say when I was in enterprise, I guess I still am in enterprise software, dashboards equals dollars.
So I like this one.
Yes.
Okay, so you use Cloud Code.
You said.
brainstorm, but brainstorm in HTML.
Give me a couple things that I can talk about.
It gave you eight ideas, including visuals and this lovely like why her, what the visual is.
And then I like the risk.
It's like it could go sideways as all good devos can.
And so you're going to pick one and then you're going to show us how you pull this through to.
a full plan on this idea.
That's right.
Yeah.
So I think what I like about HTML is like really, Claude really understands this.
And so my next prompt here was really like, OK, I asked it to make some mockups in the follow up prompt.
And then I was like, I asked it to interview me about number eight.
Right.
And so this is something that like, you know, similar to specs and PRDs, right?
Like finding out my unknown unknowns.
What do I want it to do?
I answered a bunch of questions.
And now I'm like, okay, create an HTML file as a plan that helps me visualize what the implementation plan is, include excerpts, mockups, code, whatever is needed to give me like maximum context, right?
And so then it made me this HTML file here.
Yeah, you can see now this is the plan, but it's purely in HTML.
It's got like, it started scripting out the podcast itself, which, you know, maybe I didn't need all of that, but like it.
You know, we're making a skill.
And so it, you know, fleshed out the file system.
It gave me like an excerpt of the skill.md.
It put together like a mood board as well.
Some example components.
Some of the logic here.
Yeah.
Insights and templates.
Helper scripts.
Right.
And like helping me get a sense of like, what's the important things for me to know here?
Yeah.
This is something that like.
I will actually read.
Yeah.
Yeah.
And I want to go back to Claude Code really quickly, if you don't mind, which is, you know, people are going to ask, how did it know exactly what to put into the spec?
And I just I want to go back to your prompt was very simple.
And it's so funny.
I've done.
I don't know, 75 of these How I AI episodes and they get incredible outputs and everybody's prompts like make the thing.
Hopefully it's good.
Yeah.
Kind of nice.
And so I love that this prompt is literally just create an HTML file with a plan.
Help me visualize.
You misspelled excerpts.
I did, yeah.
And you're like excerpts, mockups, code, et cetera, whatever is needed.
Yeah.
And so I do want to encourage people, you know, don't.
stress so much about what should go in the thing.
And in fact, it might change initiative to initiative.
It might be slightly different to engage you with the work, but like identifying what you want to get and then letting the model do what it needs to do will do a very high quality job.
Yeah, I think with prompting, it's like this fine balance of like, I think you want to give enough information that you get what you want, but you don't want to over constrain Claude.
And so sometimes when I see people with a lot of like overbuilt skills, kind of like, you know, you're an expert planner or something, right?
Like that is usually like outsourcing too much and constraining it.
But in this case, for example, like I really did want to make sure it gave me code excerpts.
And I wasn't sure if I did, whether it would do that, you know?
But this was really important.
But then I always need to give Claude an out.
You know, I always needed to be like, okay, like.
You asked me for this, but, you know, like there's something else I want to give you.
And so whatever is needed to give me maximum context is like my way of saying like, hey, Claude, I trust you here.
I want to just like be in the loop with you.
Yeah, I love what you say, which is I trust you because my new ending prompt is not make no mistakes.
Love make no mistakes, but that's not it.
I literally like I believe in you and trust you.
Exclamation, exclamation.
I'm like, truly, I know you are capable and I believe in you to make these decisions.
And so I think leaving that open ended sort of like whatever you got to do, I trust your judgment.
At least it makes me feel like I get better outcomes.
Yeah.
I mean, I've loved the like recent twist on this where it's like make mistakes, Claude, you know, like fall in love, you know, like, you know, make some bad decisions.
We need more happenstance in our life.
Okay.
So you built this thing.
Another thing that I want to walk people through, if you pull up the plan, because I think about this a lot and I get people that ask me this a lot, which is like, what's the future of the PRD?
What's the future of the tech spec?
Are these things separate?
Are they together?
And I think what's nice is...
They whatever you want.
Right.
And whatever you want for the audience.
So you are a single builder in the instance of this demo.
You want it all in one piece.
You want the product idea.
You want the I guess you want a 12 minute walkthrough of how you're going to demo it.
Exactly.
You want code snippets.
You want style guide.
You want that all in one thing, because this is a self-contained little project that's easier to have it all at once.
But what I can imagine in larger organizations is like, be like, put the.
PRD in one tab and put the tech spec in the second tab because maybe separate people would be reviewing that information.
And so you can really kind of like craft a ideal spec package to whatever you want with HTML in a way that markdown is a little bit more constrained.
It has to either be like one megafile.
or like separate files.
And I think this is just nicer from that perspective.
Yeah, I think that's right.
You have a lot more interactivity.
I haven't asked it to make tabs here or something, but you can easily do that.
It's like all the same to Claude, right?
Yeah.
I think one of the things on like the specs and PRDs is like, I think you're trying to find like the boundary of like what you need to know with Claude.
And for example, if you're doing something very technical, I like to do the type interfaces.
So this is like, you know, just like understanding what the types are so that.
I don't often care about the actual implementation of it.
I'm just like, OK, like the types help me understand what we're building.
And then I might edit those.
Right.
And that's like the boundary I want to interface that.
And yeah, like across the problem.
Right.
Like from the arc of the podcast to mockups.
Where do you want to interface?
Yeah.
One one other thing on this types is sort of an important input is I think types are really great.
And then really a validation criteria and set of.
tests or other ways to see if you can get what you intended to get.
And I know you all like just announced outcomes, which is really focused on this like kind of goal oriented.
You need to achieve this thing.
Do whatever you need to do.
And I think that is a piece that most product managers at least are not used to writing like the technical success criteria of a feature and then how to test your way into it.
I do those two things as well as like I care about the data model and the shape.
the types, like what's going in.
And then this is how you would test that you did it correctly.
And with those two bookends, you can like everything in the middle is kind of gravy.
So that's what I think about.
I think that's right.
We could have a whole podcast on testing, I think.
Let's do it.
Okay, round two.
We're going to get it scheduled.
Yes, yes, yes.
Yeah, my tagline there is like verification is not testing.
Yeah.
And so I think there's a lot of like...
There used to be like unit tests and things like that.
But now, yeah, verification can be like a rubric, like with managed agents and outcomes.
It can be like have cloud record a video of what it did for you, you know.
So there's a lot of depth there.
Yeah, I keep a set of like synthetic data and I like run a CLI through this synthetic data because I'm like, these are all the things that have broken in the past.
And if you get better at like resolving these broken things, then we have moved forward.
So I think there's just a lot of interesting verification and testing.
mechanisms you can do now.
We are going to, part two, pressure him to do it in the comments.
Please, please tell us.
This episode is brought to you by Persona.
You're learning to build with AI, but there's an important question you need to ask.
Who is actually using your product?
Is it a legitimate user, a bot, or a fraudster?
Brex, Figma, Etsy, and Twilio trust Persona to answer that question.
With Persona's identity verification platform, you can create branded experiences, automate fraud prevention, and know who is human online.
That makes it easy to give good users an experience that makes them feel welcome and to stop bad actors from causing damage.
And for those of you building in the AI agent space, Persona helps you verify the identities of people, businesses, and developers behind agents.
It's how companies like Lithic and Skyfire are pushing the frontier of agentic commerce.
Learn more at withpersona.com.
Okay, so you have built this, but here's the objection I'm going to get, which is Markdown is accessible, right?
I can go into Markdown, type in it, and make edits.
And so I think that is one reason is it has been so popular.
It's bridged this gap between...
machine-writable and readable, human-writable and readable at a very low level of sophistication, right?
As soon as you understand, okay, these hash signs mean headers, you're good to go on Markdown.
Yes.
I want to fix this.
How do I touch this?
How do I edit this?
Yeah, yeah.
So I think that this is a great point, right?
And I think one thing I felt with Markdown was that...
One, because I stopped reading them, I stopped editing them as well.
And so I would end up asking Claude to edit them.
And so that is the most basic form is just to be like, hey, Claude, I didn't like this part of the plan.
Can you edit it?
But let's say you want to get really in the loop and really get in depth with it.
Claude can also do that for you.
So the next prompt I had, and I forgot if it was here.
No, it was here.
Okay.
I want to create an edible HTML artifact to help me define the...
the decision rules.
So these are the rules that it's defined here on like, okay, how do you take data and turn it into, you know, a visualization?
And I think some of these are kind of arbitrary.
And so I asked it like, you know, to create an HTML artifact.
I don't like the ones we have right now.
Make this a custom UI that helps me with structure but gives me flexibility.
Design the ideal interface for this problem.
I really wasn't quite sure what it would give me.
And this is one of the fun parts of HTML2.
It's just like...
I just want to see what, what cloud like cooks up here.
And, um, yeah, this was what it gave me.
Right.
So it's like a, my own beautiful custom interface.
Um, I can sort of like, you know, edit any of these fields.
Uh, I can, you know, like hide them.
I can copy, I can, you know, add new fields here.
Um, and it gives me a markdown to, to copy back.
And so once I'm like, okay, I have this, I can copy it back into the, um, Okay, I want to pause because people are going to totally miss what you just did.
So I'm going to repeat it.
Which is you have this HTML plan.
Yep.
And there's a section in the HTML plan that is a pretty like specific table of rendering and visualization rules per data type that you could predict would be in a CSV.
Yep.
And you're like, I don't like it.
Yep.
And instead of going back into Cloud Code and being like, I don't like it, let's go back and forth and edit it in like the terminal.
Yep.
You said there's probably a way for me to interact with this particular problem that's ideal from a user perspective.
So basically build a throwaway UI for this very, it's like this is not even personal software.
This is like sub, it's like micro software on top of micro software, which is like I've made this very personalized plan and I'm taking a module in the personalized plan and zooming into it using a very custom UI.
That's going to engage me with.
the content to get to a higher quality.
I also like that it's like kind of gamified.
It's like very consumery.
Yeah, yeah.
Very consumery.
And you said in the prompt, give me the ideal UI for this to like help me engage with this.
You built this, then you get the data right.
And then you're just going to bop it back into the file.
Yeah, exactly.
So fun.
Is this how you're building now?
Actually, it is.
Yeah.
And do you have any challenges with...
Like, how are you passing this around from a collaboration perspective?
Or is it just like this is the way a single threaded product or engineering leader can get something done?
It's you're engaging with yourself and with the model.
And so you feel like you can own things full stack.
Or do you hit friction points with collaboration?
Like when somebody needs to get input on this?
Yeah.
Or you want input?
Sure.
Yeah.
I mean, I think on the scale of an implementation plan, it's way better.
Yeah.
whatever, AWS or something.
And then you just share the link around.
And so definitely the like likelihood of like, I don't know, Kat or Boris, like reading this is like a hundred times better.
Right.
And so I think that really helps me like present this.
I also just, you know, somewhat related.
I use it a lot in like collaborating overall.
So for example, You know, I report to Kat.
And so like every week I send her a weekly status update in HTML of everything I've done.
I get called to read my Slack and just like create this message.
And like she actually gets to read it and I don't have to spend that much time on it.
You know, my gosh, new competitive, new internal competition is showing up.
It's not just who is building the best product.
It's who's building the best product.
That goes into building the best product.
And like who is building the best product to represent themselves to the manager.
But I mean, I think why you do that is not artificially for fun.
It is that it is just a much more effective way to communicate across a company is with content that is engaging and at the right level of detail and consumable.
And we're all pretty good at reading websites.
Yeah, exactly.
I think this is like.
When I think of like abundance, you know, and like, you know, we talk about like Javon's offer software, like, oh, like software gets cheaper.
What do you do?
I'd say like the amount of tokens I produce that go into production code are like extremely small.
It's like 1% or something, you know, but like I'm generating so many more tokens like this, like my dashboards, my custom interfaces, like really trying to get a sense of like, what do I want to do?
And yeah, it's like I have everything I'm interacting with is so beautiful.
And I think.
My hope is that it also like translates into what I produce in the end.
Right.
It's like more in the loop.
It's more beautiful.
It's more like, you know, like what me and Claude working together.
Yeah.
And I like this because I've been in the product game for quite some some time, many decades.
And people used to get so wrapped around the axle on like what's our source of truth for specs and what's our source of truth for PRDs.
You know, is all this information in some centralized place that we can all access it?
And is it all in the same format?
Is it all in the same template?
And there were these arbitrary rules because creating this content was relatively expensive.
Consuming it was certainly expensive.
Finding it was really hard.
And I think when all of that cost goes to, like, functionally zero, although we're all paying our, I call them our quad chits.
We're paying our quad chits.
But you can.
kind of put stuff wherever in whatever format, because we know these models are very good at using tools to discover the context that they need.
And so I do think there's this fun moment where you really up, you like up level the things that you should care about, which is like, what is the content of the plan?
Is it a good idea?
Do we feel like it's going to be executed well, as opposed to like, I can't put a interactive markdown document in our.
you know, blessed document repository.
And so I have to have like another asset somewhere else.
And so I just, I like this idea of just-in-time documentation, very, very high quality, some throwaway software, which is nice.
Like it's cheap.
So you can toss it.
And then I like, you know, the executive is like, what if we can't ever find this again?
I'm like, oh, Claude can find it for us.
It's fine.
Definitely.
And then do you feel like this results in better?
Like, how would you build off of this?
Would you say, plan's good, let's go?
Yeah, I think so.
I didn't hit implement on this.
But yeah, I would basically use this as an artifact.
And so I would clear context.
And I would say, like, here's a plan.
You know, implement it.
You could also have, like, you can also use this as a source of checking the truth.
Right.
And so, again, a benefit of HTML is, like, I've got a little.
mock up here as well so right i can have the verification or i can have the verification agent check like hey what did i intend to do yeah right and what actually came out in the output right um so yeah i think this is like really uh helps claude being more in the loop um i've got some other examples of plans here that we can let's see it yeah this is like a post i'm working on so like uh it's just like different ways i'm i'm using uh cloud code Sorry, using HTML with Cloud Code.
And one of my favorites is this living design system.
And so it's this idea that, like, you know, oftentimes when I am making, let's say, a new app in the Anthropic design system, right?
Like, Cloud Design does this very well.
You link a GitHub repo, and you, like, it will extract the design system from it.
Right?
And, yeah, I saw Nate did that.
I'm like, oh, so smart.
What this does is like basically I have an HTML file that represents my design system.
You can see the colors here, typography, spacing, radius, core components, right?
It's a fairly small one.
But once I have this, I can basically start passing this around.
So I go to a new project.
I'm like design system dot HTML, right?
Instead of like design dot MD or something.
And it's got this like compressed understanding.
And you can literally just point.
Claude at a folder in your thing and be like, hey, find a design system here, create an HTML artifact and pass it around.
I love this.
I do this as well.
I will give you my like advanced mode version of this, which is I use Claude Design.
I pull in my both my marketing site repo and my app repo, which have like some expressions of the same design system in.
I say make the design system.
Then I actually make it ask, ask it to make a design system or a style guide.
But I want it at the component level.
And so we have like colors, all this stuff.
But we also have components because there's some tweaks in how you want the design system implemented in particular components.
And then I drop that into the repo.
And then, yes, I say exactly this.
Reference the design system.
The advanced thing that I do that I think is really useful for people who have to interface with marketers.
is I have what I call a, God, what do I call it?
It's like a component visualization page, which is like the 25 components of our app in action and interactable in a page.
So a marketer can go in and get the component in the form factor.
It needs to look quote unquote real.
And then you can download a transparent.
PNG and like drop it in a deck or drop it in a video.
And I know you or we use that as a source of truth for like re-motion videos.
And so I love this idea of like this living design system and this living design repository.
It's great for code, but it's also great for marketers, for designers, because one of the hardest things is is getting versions of your app that look real.
Yeah.
And you can use HTML to do that.
Yeah, exactly.
I think there's also something here around like component variations, which I thought was fun where it's like, yeah, like you create a component you want to see like, oh, like what if I change the padding or what if I change the border, you know, solid, things like that.
Like these are like a pretty simple, like, you know, way of just playing with this.
This is also Claude design like, right?
Like where you create these little components or these little knobs and sliders.
But yeah, you can imagine, one, this is like the abstract of like, oh, like what's the interface for this thing that you're trying to do and how can you visualize it?
And yeah, there's not a tradeoff between like being nice, pretty for you and understand being nice for Claude.
You know, like they're really the same, right?
And you're making me think of one thing that I love in Claude design that I think you could bring into your plans.
Again, it's one of these features that like sounds...
truly cuckoo bananas to build, but it's totally possible and easy to do, which is I love in Claude Design.
Once you have your design going, you can like comment, you can circle things.
And there's no reason you can't do that in a plan.
Right.
I was like, oh, how would you interact with this?
It's like, oh, just build an arbitrary like comment thing into it and say people are going to leave comments on any aspect of this.
And when they do, and then they submit like fix, it fixes the core thing.
And so I think people getting really creative with what interaction models you can do between content and code is really fun.
Yes.
Yeah.
I mean, you could easily imagine that you did this plan as like a, like almost a lightweight Figma dashboard or something where you just ask it to like, Hey, make a canvas, make a bunch of things.
Let me comment on it.
And then give me a place to copy out my comments into something that I can paste back into cloud code.
Yeah.
And we did an episode recently.
with the Stripe team and they built their own vibe coding platform.
And they said what they loved about it, which I think really applies here, is they have just a particular way they want to review products.
And they have a particular way they want to run design review and a particular way they want to run spec review.
And by building it in HTML, they can actually shape the tool to how they want the team to run, which I think is really compelling to people.
I love this.
So just to wrap for people, pull up Cloud Code.
Ask it to make you, give you some ideas, brainstorm ideas, but brainstorm them in HTML.
That's right.
Pick an idea.
Yep.
Plan it in HTML.
Pick a part of that idea you don't like.
Have it create a micro app to edit in HTML.
And then some like bonus things is use Cloud Design.
Make a design system, but not only that.
Use HTML to encode that design system in your repo so it can be referenced at any time.
Design.md is dead.
Long live design.html.
Did I get it right?
Yeah, I think that's right.
I'm pretty good.
Okay.
Well, this was so fun.
Before we get you out of here, back to this amazing event, a couple of lightning round questions.
One, I have to, I ask everybody, there's three tabs in Claude desktop app.
Yeah.
One is your favorite tab?
It's got to be code.
I love the team as well.
I'm really close friends with them.
Yeah.
Okay.
So, so, so code.
I thought it would be on brand.
Okay.
Second thing, we were at this amazing event.
What is the thing that you're most excited about or that you saw or heard today?
I think obviously we had a big announcement at the start of the day.
Our partnership with SpaceX, bringing more compute online.
I think, yeah, I'm excited for, you know, we also said we are thinking about orbital data centers.
I love it.
Yeah, you know, incredibly sci-fi.
But, you know, it could actually happen.
So, yeah.
I know.
We were watching this moon mission with my kids who are like kind of elementary school.
And I'm like, would you want to work in the moon?
Would you want to work in the moon mines?
Because I think it's coming.
Yeah.
Orbital, orbital.
That's that'll be next year's demo.
You and I will come back and we'll do this.
We'll do HTML.
We'll do testing and then lunar data model modules.
That's right.
Perfect.
OK.
And then my last question.
Very important.
I love that you just talked to Claude like a person.
Yeah.
When Claude is not listening, not giving you what you want.
Yeah.
What's your prompting technique?
Do you yell?
No one in athropic yells.
That has been my experience so far.
So you'd be the first to admit it.
Yeah.
No, I definitely don't.
I think that like there are a couple of things here.
I do sometimes message people and I'm like, hey, like, seems like you have a bug.
Can you send me your transcript?
And they're like, it's not the best side of me.
Yeah.
I think that like.
Yeah, I don't, I don't yell at Claude.
I think that like, we've also done some interesting research recently about like emotions and in Claude and just sort of like this idea that like once you when you say things with a certain emotional charge, it also like activates different features inside of Claude code.
I don't think anyone's done this like a B test of like, which, like, you know, if you're mean to Claude, is it better than without it or not?
But I'm just like, let's err on the side of like, you know, not or like, what's the thing I prefer to exist, you know, and I'd prefer.
If you're like nice and friendly to Claude that you get better output.
All I've seen is if you store a border on Stern to any of these models, their reasoning gets really sad.
It's like, oh, the user is right to be so disappointed in me.
I'm like, oh, I don't want to read that.
I don't want to see that.
Yeah.
Thinking traces are tough.
I usually give the model some privacy.
I'm like, I'm not going to read the thinking traces.
It's like none of your business.
Yeah.
I had somebody else on.
I feel like it was Hillary who was like.
Just like an employee, how you get your work done is none of my business.
I don't even want to know.
We just collapse those things.
Well, this has been so fun.
Thank you for showing us the way.
Where can we find you and how can we be helpful?
Extremely online at X.
Yeah, I'm at TRQ212.
And yeah, just tag me if you have, you know, anything with Cloud Code.
I'm happy to help.
Perfect.
I am living proof.
This man is happy to help.
Well, thank you for joining How I AI.
Thank you.
Thanks for having me.
Thanks so much for watching.
If you enjoyed the show, please like and subscribe here on YouTube or even better, leave us a comment with your thoughts.
You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app.
Please consider leaving us a rating and review, which will help others find the show.
You can see all our episodes and learn more about the show at howiaipod.com.
See you next time.