The 6-Cell Prompt That Makes AI Build a Whole Website You Can Double-Click Open
Most AI-generated web pages fail for beginners at the prompt stage, not the code stage; this gives Western developers a copyable prompt structure and a zero-dependency single-file pattern that sidesteps hosting, CDN, and local-file pitfall entirely.
AI fails at making a company website not because it can't write HTML, but because the person asking didn't specify three things: the page sections, the visual style, and the deliverable form. This guide turns that into a six-cell checklist — who sees it, what sections, what style, what sizes, how to deliver, how to accept — and feeds it to an AI as a copy-ready prompt.
Each cell forces verifiable specifications: style becomes numbers like "content area 1120px, section spacing 88px, one primary color"; delivery becomes "single index.html, all CSS and JS inline, zero external CDN or fonts"; acceptance becomes countable rules like "no horizontal scrollbar at 1440px or 390px." A full 13.6 KB runnable file demonstrates the result — 6 semantic blocks, zero external requests, zero console errors.
Local opening is handled too: show file extensions, save with UTF-8, handle the `.txt` trap, and a troubleshooting table covers symptoms like blank screens, garbled layout, and CORS errors from `file://` fetch calls. The solution is to avoid `fetch` entirely and write data as JS arrays.
Treating AI as a contractor — giving it a floor plan, material list, and acceptance criteria — is more effective than treating it as a magic generator that reads minds.
The real bottleneck for AI-generated websites is not AI capability but the human's ability to make design requirements countable and testable.
Single-file output with zero external dependencies doubles as a distribution mechanism: a zip file can ship a full website to anyone without hosting.
The advice to avoid fetch() for local files shows how AI tools can silently produce code that breaks under file://; knowing the runtime context matters as much as the prompt.
Awwwards-winning aesthetics are often at odds with usability, which is why the guide explicitly separates visual rhythm from interaction complexity.