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 property listings as a homes-for-sale page with filters, a synced map and a detail view, following the structure of a real estate template I am copying.
Live template to study: https://templateinterface.com/templates/real-estate-listing/
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/real-estate-listing/index.html, https://templateinterface.com/templates/real-estate-listing/styles.css and https://templateinterface.com/templates/real-estate-listing/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, section links (a Menu button on narrow screens) and a Saved button that switches the results to saved homes.
- Search band: page title, three figures, and a filter card with area, minimum and maximum price, a bedrooms segmented control, and More filters (type, must-haves, hide homes under offer).
- Results: a heading with a plain-language summary of the search, sort, and a List or Map switch on narrow screens; a grid of cards beside a sticky map with price pins; an empty state.
- Each card: image, a badge, a save heart, price, address, bedrooms, bathrooms and size, a teaser and when it was added.
- Detail view as a dialog: gallery, key facts, an energy rating, a mortgage calculator and a viewing request form.
- Area guide: four area cards, each with a Show homes in button.
- Valuation: a band with three figures and a valuation form, then a footer with the office address and hours.
Design direction (use this palette only if my site has no branding):
- Warm off-white ground (#f7f4ee), dark green-grey ink (#1d2a2a), a deep teal accent (#0f5c55) for bands and actions, and brass (#d3a64a) for highlights.
- A classic serif for headings (Baskerville or Constantia) with Segoe UI or Arial for body text and figures.
- Drawn houses and a drawn map instead of photographs.
Behaviour:
- Filters update the cards, the map pins, the count and the summary sentence together.
- Hovering or focusing a card highlights its pin, and choosing a pin scrolls to its card.
- Save toggles with aria-pressed and a toast confirms it. The detail view is a native dialog that returns focus to its card.
- The mortgage calculator updates as you type. Forms show a demo notice if there is no 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.