Most advice about writing good prompts is a list of adjectives: "be specific," "give context," "describe the outcome." True, and useless, in the way that "eat better" is true and useless. So instead of another list, here's one actual prompt, pulled from a build queue a few weeks back, with the identifying details changed but the structure and the words kept intact. Eighty-three words. It became a working booking site in one pass, and almost nothing about it was an accident.
"I do private chef dinners for small groups in Denver — like 6 to 12 people, at their house. I want a site where people can see sample menus, check dates I'm free, and pay a deposit to hold the date. Make it feel expensive, not like a caterer's website. I only do three bookings a week so don't make it look like I need the business. Also I want to show up when people search 'private chef Denver' but near Cherry Creek and Wash Park, not the whole metro."
Let's take it apart in the order it was written, because the order matters almost as much as the content.
"I do private chef dinners for small groups in Denver"
The opening line is doing three jobs at once and none of them look like instructions. It sets the category (private chef, not "catering," not "restaurant" — those are different search intents and different design languages). It sets the scale (6 to 12 people rules out banquet-hall energy and rules in something closer to an intimate dinner party). And it sets the geography, which will matter a lot more later than it seems to here. Nobody tells you to extract a category, a scale, and a location from one sentence. You just have to notice that all three are load-bearing.
"See sample menus, check dates I'm free, and pay a deposit to hold the date"
This is three features crammed into one breath, and it's the sentence most likely to get over-built. A less careful read turns this into three separate pages with three separate navigation items — a Menus page, an Availability page, a Payments page — because that's what "features" sound like when you list them. But read as a sequence, it's actually one flow: browse, pick a date, commit. Splitting it into three destinations adds three places for a visitor to bounce. The site that shipped has one page that does all three in order, because the client described a journey, not a sitemap, even though she used the grammar of a feature list.
"Make it feel expensive, not like a caterer's website"
This is the least actionable-looking sentence in the whole paragraph and it's the one that decided the most. "Expensive" isn't a color palette or a font, but it does rule things out: no percentage-off banners, no "Book Now!!" urgency copy, no stock photography of smiling families around a table. It argues for a lot of negative space, one strong photograph instead of a gallery grid, and pricing presented as a number stated once, quietly, rather than a comparison table daring you to pick the middle tier. "Not like a caterer's website" is doing real work here too — it's a negative example, which is often more useful than a positive one because it tells you what to actively avoid rather than leaving you to guess at a mood board.
"I only do three bookings a week so don't make it look like I need the business"
This is the sentence that does more work than the rest of the paragraph combined, and it's the one a generic prompt-writing checklist would never surface, because it's not a feature or a design note. It's a business fact, and it reverses the usual instinct. Most small-business sites are built to look busy — testimonial carousels, "as seen on" logo strips, a countdown to the next available slot — because busy reads as trustworthy. Here the opposite is true: scarcity is the value proposition. A calendar that shows three open dates a month, presented plainly, is more convincing than one padded to look full. The whole site avoids anything that smells like it's trying to convince you. No urgency copy, no "only 2 spots left" banner. The confidence is the sell.
"Show up when people search 'private chef Denver' — but near Cherry Creek and Wash Park, not the whole metro"
The client asked for a search term and then immediately narrowed it, which is unusual and worth paying attention to. Most people who mention SEO in a prompt say the broad version and stop. Here the correction came unprompted: not Denver, two specific neighborhoods. That's a service-area business talking about the six-mile radius she'll actually drive, not the metro she'd like to rank for. It shaped the copy (neighborhood names appear in the actual sentences, not stuffed into a footer), the structured data (a service-area business type, not a storefront), and — the part that's easy to skip — it meant NOT writing broad "Denver" copy that would have technically been true and practically useless, since ranking for the whole metro and then disappointing everyone outside a 15-minute drive helps nobody.
The thing she didn't say
Here's the part a teardown usually skips: what's missing. There's no mention of dietary restrictions, no cancellation policy, no price range. A prompt that thorough about tone and geography going silent on allergies isn't an oversight to route around quietly — it's a gap worth asking about, because a private chef taking a deposit for a dinner with a nut allergy in the room is a liability question, not a design one. The build shipped with a placeholder allergy-disclosure field and a follow-up question back to her, rather than either inventing a policy or leaving the gap open. The instinct to fill every silence with a guess is exactly how builds end up confidently wrong about something the client would have answered in one sentence if asked.
| Fragment | What it actually said | What it shipped as |
|---|---|---|
| "6 to 12 people, at their house" | Scale and setting | Copy and photography scoped to intimate dinners, not events |
| "menus, dates, deposit" | A sequence, not a list | One page, three steps in order — not three pages |
| "expensive, not like a caterer's website" | A negative example | Quiet pricing, one hero photo, no discount language |
| "three bookings a week" | A business constraint | Scarcity as the tone, not a bug to hide |
| "Cherry Creek and Wash Park, not the whole metro" | A self-correction on scope | Service-area schema + neighborhood copy, no broad-metro padding |
| (unsaid) allergies, cancellation, price range | A gap | A follow-up question, not an invented policy |
What actually shipped
One page. A calendar that shows real open dates instead of a "book a consultation" form. A menu section with three sample dinners instead of a full catalog. No pricing table — one line, stated once, near the deposit button. It ranks for the two neighborhoods it was asked to rank for and doesn't try to rank for the metro it wasn't. None of that came from a prompting formula. It came from reading a business-owner's 83 words the way you'd read a conversation instead of a spec sheet — noticing which sentence was a feature, which was a mood, which was a fact about her calendar that happened to double as a design brief, and which sentence she never got around to writing at all.
