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 business's website as a clinic site: urgent help first, treatments with fees, the clinicians, an insurer and plan checker, in person or video appointments, and new patient registration, following the structure of a template I am copying.
Live template to study: https://templateinterface.com/templates/clinic-practice/
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/clinic-practice/index.html, https://templateinterface.com/templates/clinic-practice/styles.css and https://templateinterface.com/templates/clinic-practice/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:
- An urgent strip at the very top with the same-day phone number.
- Header: logo, four section links, a dark or light mode button and a Book button. Below about 860px the links fold into a Menu button.
- Hero: who is being accepted, the promise in one line, register and book buttons, and three routes (urgent today, appointment this week, join the practice).
- Treatments and fees: a filterable table with visit length, private fee and plan fee.
- Clinicians: qualifications, registration numbers, what each does best and the days they work.
- Insurance and plans: an insurer checker that says whether the practice claims directly, beside the practice's own plan.
- Appointments: in the practice or by video, a reason list that changes with the mode, and the next free times.
- New patient registration in three parts (about you, medical history, consent) with a progress list.
- Finding us with access details and opening hours, then the footer.
Design direction (use this palette only if my site has no branding):
- Clean white and pale blue grounds, a deep clinical blue (#1d4f86) for actions, a warm coral only for urgent.
- Segoe UI or the system sans throughout, generous line height, rounded but not playful corners.
Behaviour:
- The treatment filter shows one group at a time and announces how many are shown.
- The insurer checker states plainly whether claims are direct, refunded or not accepted, and what to pay on the day.
- Video mode offers only reasons that can be handled by video.
- Registration validates each part before moving on, keeps answers when going back, and ends with a demo notice if there is no backend.
- Forms validate inline, move focus to the first problem, and 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.