Your agent wrote the page. One click makes it client-ready.
Plain HTML in, considered page out — same content, same link. The pass scores the page against Stacktree's written design standard, rebuilds it keeping every fact, and shows a before/after preview with the direction it chose. Nothing changes unless you apply.
On every plan · about a minute a run · previews are free to discard
- Shipped the export fix.
- Closed four support threads.
- Draft the pricing FAQ.
- Review the backlog with Sam.
The direction
“Treat it as a quiet internal status memo — a single confident teal accent, warm ink-on-paper neutrals, and hand-drawn status dots that make progress legible at a glance.”
A real run, compressed — the actual pass took 60 seconds and this is its actual direction.
How do you make an HTML page look professionally designed?
Host it on Stacktree and run the design pass: it reads the page, scores it against Stacktree's written design standard, rebuilds it with every fact and link intact, and shows a preview you can toggle against the current page. Apply keeps the same URL. If the page already has a real design, the pass says so and declines rather than restyling it into something worse.
Made for the page nobody designed
Most HTML worth sharing was never designed: an agent's 5 a.m. report, an export, a page hand-written for its facts rather than its looks. It reads fine and looks like 1996, and the person opening it can't tell diligence from default fonts. The design pass exists for that exact page. It is not a theme switcher; it rebuilds the page the way a designer would, and tells you the direction it took in one sentence, because a restyle you can't reason about is a restyle you can't trust.
Preview first, apply second, abstain when right
The pass never touches the live page on its own. It produces a preview with a before/after toggle, and its verdict can be "leave it alone": pages that already carry a real design get an explicit abstention, because the honest finding from testing was that blind restyles make designed pages worse. Apply routes through the normal replace path — same URL, all guards intact — and if the page was edited while the pass ran, the stale preview is discarded rather than applied over newer work.
For the fleet, not just the click
The one-click pass and connected agents share the same brain: the design guide is a served document (GET /design-guide, or the design_guide MCP tool), so an agent that publishes daily standing reports can do its own rebuilds with its own model, to the same standard. The click is for humans who got handed plain HTML; the guide is for pipelines that should never ship plain HTML in the first place.
Frequent questions
What is the design pass? +
Does the design pass change my content? +
What if my page is already well designed? +
How long does it take, and what does it cost? +
Can my agent use the design pass? +
Does applying change the URL my client already has? +
Related guides
- For developers The publish primitive, the design guide endpoint, and the standing-report pattern.
- Every agent integration MCP, skills, n8n, connectors — the ways agents publish what the pass then polishes.
- Share HTML with a client The delivery side: gated, branded links for the page you just made client-ready.
- Pricing The design pass is on every plan; what the plans actually meter.
Plain page in. Client-ready page out.
Publish free, run the pass, keep the link. No card, about a minute.
Sign up free →