Hi PH — Yavuz here, maker of web-builder. I work as an engineer at Insider and kept hitting the same wall on side projects: I'd open a terminal to spin up a small marketing page or a quick tool, and lose forty minutes deciding between Next, Astro, SvelteKit, plain HTML, Tailwind vs not, Vercel vs Cloudflare. The decision fatigue killed more side projects than the actual work ever did. So I built this for myself. The premise: I describe the goal, the plugin's agents decide the stack, and I get a real project on disk — not a sandboxed preview I can't own. What I learned building it: keeping the agents stack-agnostic (zero hardcoded framework names in the plugin code) was harder than expected but pays back every time the JS ecosystem moves. Next on the roadmap: custom domain automation, AI-generated images instead of Unsplash placeholders, and a test framework setup pass. It needs a Claude Code subscription to run. Source is MIT. Happy to answer questions — would love feedback on the revision flow specifically.

web-builder

Describe a website, get a deployable project back.

Describe a website, get a deployable project back.