Open Claude Code in your own website's project folder, then copy this prompt and paste it in. It rebuilds the layout and interface only: your existing colours, fonts, logo and voice are kept, and this template's palette is used only if your site has no branding yet.
Rebuild the layout and interface of my restaurant, cafe or bar website as a single mobile-first page, following the structure of a trattoria template I am copying.
Live template to study: https://templateinterface.com/templates/restaurant-site/
Before writing any code, open that link and read through it in detail. Analyse the rendered page and its source files in the same folder (https://templateinterface.com/templates/restaurant-site/index.html, https://templateinterface.com/templates/restaurant-site/styles.css and https://templateinterface.com/templates/restaurant-site/script.js): the section order, the layout grid and breakpoints, every component, the spacing and type scale, each interactive state, and how the script behaves. Summarise what you found before you start. Treat the live template as the source of truth for layout and interface, and the notes below as a summary of it. It is not a source of branding: the branding rule still applies. If the link cannot be loaded, say so and work from the description below.
Branding rule, which overrides anything below: this template supplies layout and interface only. If my site already has branding (colours, logo, typefaces, icon style, photography, tone of voice), keep all of it exactly. Read my existing stylesheets and pages first, list the brand colours and fonts you found, and map them onto the roles this layout needs (background, surface, text, muted text, accent, accent on hover, border, success, error). Where a role has no brand colour, derive one from the brand palette rather than borrowing the template's. Check that every text and control pairing still meets WCAG AA contrast with my colours and adjust shade, not hue, if one fails. Only if my site has no branding at all, use the palette and type described in the design direction below.
Page structure, in order:
- Header: logo, an open-now pill computed from the visitor's clock and my opening hours, three section links, and a Book a table button. Links fold into a Menu button below about 860px; hide the pill below 640px because the hero repeats it.
- Hero: the name set very large, one sentence pitch, Book a table and See the menu buttons, and the open-now line.
- Menu: short intro (portions, prices, service), a specials board, vegetarian, vegan and gluten-free filter toggles, course tabs, dishes with dotted leaders to the price and dietary tags, a count of dishes shown, an empty state, and an allergy note.
- Story: a short kitchen story with two or three figures.
- Hours and directions: an hours table with today highlighted and an open or closed badge, a simple map, address and phone, and how to arrive by public transport, by car and step-free.
- Booking form: party size, day, then time slots generated from my hours (fully booked slots visible but disabled), name, email, notes, and a confirmation state.
- Footer: address, hours in brief and links.
Design direction (use this palette only if my site has no branding):
- Warm paper background (#fbf6ea), dark brown ink (#2a2118), a deep red accent.
- A high-contrast Didone display face (Bodoni or Didot, falling back to Georgia) for the name and headings, and a humanist sans (Gill Sans, falling back to Segoe UI) for body text.
- Menu styled like a printed card, not a grid of photo tiles.
Behaviour:
- Open status updates from the local time and handles a closed day and hours past midnight.
- Course tabs follow the ARIA tabs pattern with arrow-key support.
- Dietary filters combine, update the shown count, and announce changes to screen readers.
- Booking time slots rebuild when the day changes; the form validates inline and shows a demo notice if there is no booking backend.
- A sun or moon button in the header switches between dark and light mode. Derive both modes from my site's branding, open in dark mode by default, remember the choice, and set it before the first paint so the page never flashes the wrong mode.
Build rules:
- Plain HTML, CSS and JavaScript. No framework, build step or external resources unless my project already uses them, in which case follow its conventions.
- Mobile first: one column at 320px with no horizontal scrolling, widening at breakpoints that suit the content.
- Semantic landmarks (header, nav, main, footer), one h1, headings in order, visible labels on every field, and a visible focus style on every control.
- Every interactive state (hover, focus, active, disabled, selected, error, empty, loading or success) is designed, not left to browser defaults.
- Respect prefers-reduced-motion.
- Any form without a real backend says so visibly when submitted instead of pretending to send.
- Use my real content. Where you have none, write short, clearly marked placeholder copy for me to replace, never invented facts presented as real.
When you finish, check the page at 375px and 1440px, confirm there are no console errors, and list anything you could not keep from my branding.