claude code and the case for html instead of markdown
small workflow idea that feels obvious after you hear it:
stop asking claude code for giant markdown specs when what you actually need is something people will read.
thariq from the claude code team wrote about preferring html as an output format. not because markdown is bad. markdown is still great for readmes and docs that live in git.
but for ai-generated work artifacts, html can be much better.
pr walkthrough with colored risk levels
architecture explainer with a diagram
design options in a comparison grid
onboarding page with collapsible sections
one-off ticket sorting board with drag and drop
create a single self-contained html file that explains this feature. include a summary, diagram, annotated code snippets, risks, and next steps.
html is for reading, comparing, and deciding.
that split feels like the useful part.
for teams using claude models across different workflows, EvoLink gives one api endpoint for claude and other model families.