Case Study: A Cinematic Restaurant Website, Generated by Claude in One Shot

"Ogień i Zioła" is a fictional Polish restaurant in Poznań, built entirely by Claude from a single prompt and published on Hostilo — no revisions needed. Unlike our Tetris case study, where getting the logic right took several rounds, this one worked on the first attempt. Here is the exact prompt, and why the difference matters.

The brief

The goal was a premium, editorial-feeling restaurant website: full-screen cinematic hero, sticky navigation, a story section, interactive menu tabs across four categories, a chef profile, a reservation widget with real form validation, a CSS-only image gallery, hours and location, a newsletter signup, and a footer credit — all in a single HTML file, no external libraries, no images, no backend.

The exact prompt (copy it, try it yourself)

This is the full, unedited prompt sent to Claude. Nothing was added afterward — this is what produced the finished site:

Live example

See the result: restauracja.hostilo.page

Why this one worked in a single pass

Our Tetris case study needed several rounds of fixes — real interactive logic (collision detection, rotation, scoring) tends to have edge cases that surface only when you actually run the code. This restaurant site is a different kind of project: it is content- and layout-heavy rather than logic-heavy. Its only interactive pieces — tab switching and form validation — are simple, well-understood patterns any capable model handles reliably.

The prompt itself also did a lot of the work. It listed every section explicitly instead of describing the site vaguely, stated the technical constraints up front (single file, no external libraries, no images, no APIs), and specified the tone ("cinematic, elegant, warm and premium") instead of leaving style to guesswork. That combination — a content-heavy brief, explicit constraints, and a clear tone — is exactly the pattern covered in our guide to writing single-file AI prompts.

From Claude to a live link

The publishing step was identical to every other example on this blog, regardless of how detailed the generated page was: copy the full HTML from Claude, paste it into the Hostilo editor, click save. The site was live immediately, with no build step and no separate hosting setup for the animations, tab logic, or form validation — it is all just HTML, CSS, and JavaScript in one file.

The takeaway

Not every AI-generated project needs iteration, and not every one avoids it — it depends on what you are asking for. Visually rich, content-driven pages with simple, standard interactions (tabs, forms, smooth scrolling) tend to work in one pass, especially with a detailed, well-structured prompt. Projects with real logic — games, calculators, anything with state and edge cases — are more likely to need a few rounds. Either way, publishing itself stays a single, fast step once the code actually works.

Frequently asked questions

What AI tool built this restaurant website?
Claude, from a single detailed prompt. The full prompt is included in this article.

Did it require any fixes or revisions?
No. Unlike the Tetris case study, this site worked correctly on the first attempt — no follow-up prompts were needed.

Is Ogień i Zioła a real restaurant?
No. It is a fictional restaurant created specifically to demonstrate what a single AI prompt can produce for a visually rich, content-heavy website.

Does the reservation form actually book a table?
No. It validates required fields and shows a realistic success state, entirely in the browser — there is no backend or real booking system behind it, since none was requested in the prompt.

Why did this work in one shot while the Tetris example needed iteration?
This project is content- and layout-heavy with simple interactions (tabs, form validation), while Tetris involved real game logic with edge cases like collision detection. Logic-heavy projects typically need more iteration than visually-driven ones.