Blog
Aim before you fire.
Six parallel sessions can build a website astonishingly fast. The Design tab exists to make sure they are all building the same one.
The failure mode is aim, not speed
Watch someone build a website by prompting an agent and you see the same loop: generate, look, wince, re-prompt. Every iteration quietly redefines the target. The agent is fast, but fast toward what? Nobody wrote it down, so the answer changes with every message, and the tenth version often looks worse than the third.
This gets more expensive, not less, when a whole fleet does the building. Six sessions iterating blindly do not converge six times faster. They diverge.
The Design tab is our answer: a website builder that designs before it builds. You settle the theme first, then the page plan, and only then does the fleet write code. By the time a single file exists, there is an agreed target for the work to be measured against, which is also what lets verification mean something. We wrote about the tab itself when it shipped; this post is about why it works in that order.
The order
Theme, plan, build.
Decisions are sorted by how expensive they are to change later. The theme touches every page, so it is settled first, while changing it costs nothing. The page plan fixes scope, so it comes second. The build comes last, because code is the most expensive place to discover a disagreement. The fleet inherits a target instead of inventing one, and the mission becomes a checklist rather than a negotiation.
# the order of operations
1 theme settled while changes are free
2 page plan scope agreed, page by page
3 build dispatched across the fleet
4 verify checked against the targetWhat you get
Why an agreed target wins.
Parallelism that converges
With the theme and plan fixed, six sessions can take different pages and still produce one coherent site. Without it, parallel work is just parallel guessing.
Cheap disagreements
Hating a palette in the Design tab costs a click. Hating it after the fleet has built ten pages costs a rebuild. The tab moves the argument to where it is cheap.
A real definition of done
Verification needs something to verify against. A settled plan turns "does this look right" into a question with an answer, which is the difference between finished and merely stopped. Good ground rules for any greenfield build.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.