A page is an argument, not a layout
A style gallery tells an AI what a page should look like. It does not tell it what the page has to accomplish, which section answers which objection, or how many items each section may contain. Those three things are what separate a page that reads as designed from one that reads as generated.
Each recipe below fixes the order, exposes the few variables worth changing, and lists the specific ways that page type fails. Copy the assembled prompt, or edit the variables first and copy the version you get.
SaaS Landing Page
Ten sections, one argument. The order that survives a cold visitor, plus the six words the prompt bans because they make copy read as filler.
02Portfolio / Case Study Site
Six projects, each carrying a constraint and an outcome. The characteristic failure is a wall of thumbnails that proves nothing about how you think.
03Product Detail Page
Gallery, buy box, variant, trust. The page where a forty-pixel mistake costs a sale, and where AI reliably invents five-star reviews.
04Analytics Dashboard
One question per screen. A KPI row, one chart, one table — plus the empty, loading and error states that generated dashboards always skip.
05Blog / Editorial Site
A 62-character reading column, an index that ranks by depth rather than date alone, and an article template that survives footnotes, code and long quotes.
06Launch / Event Page
A one-pager where four facts decide everything: what it is, when it is, where it is, and what happens when you click. Most generated versions hide all four behind a hero image.
07Pricing Page
One recommended tier, numeric limits instead of the word unlimited, and a comparison table short enough to read. Where most AI pricing pages quietly lie.
08Documentation Site
Three columns, one of which does not scroll. Grouped navigation, a code block that never widens the page, and the answer in the first two sentences.
09Onboarding Flow
One question per screen, validation that does not punish, and a skip that actually skips. The flow where a badly timed field costs a signup.
10Careers Page
A role list with salary ranges, a hiring process with a timeline, and one honest paragraph about what the job is actually like. The paragraph is the part that filters.
11Contact Page
One channel, three fields, and a sentence about what happens after you press send. The page that decides whether a stranger believes a human is behind the site.
12Error and Empty States
Five screens nobody designs: 404, 500, maintenance, empty search, no permission. One template, one plain sentence, one way forward — and the correct status code.
Nothing in this category yet.
Why a recipe and not a prompt pack
A prompt pack gives you a hundred sentences and no way to tell which one works. A recipe gives you one page type, the reasoning behind its section order, and the variables that genuinely change the outcome. When a build goes wrong you can point at the section that failed instead of rewriting the whole prompt.
Every recipe here follows the same four-part shape: goal, structure with counts, style block, constraints. The style block is the part most prompts omit, which is why generated pages so often look like a template with a different accent colour.