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 class studio site: a weekly timetable you can filter and book from, spaces left and waitlists, memberships and class packs, coaches and a free trial, following the structure of a template I am copying.
Live template to study: https://templateinterface.com/templates/class-studio/
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/class-studio/index.html, https://templateinterface.com/templates/class-studio/styles.css and https://templateinterface.com/templates/class-studio/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: wordmark, four section links, a dark or light mode button and a free trial button. Below about 860px the links fold into a Menu button.
- Hero: the promise, trial and timetable buttons, and the next classes today with spaces left.
- Timetable: a strip of the next seven days, filters for type, level and time of day with a count of classes shown, and a list of classes with time, length, coach, level, spaces left and a Book or Join waitlist button.
- Memberships and class packs: a monthly or yearly switch and three plans, the middle one marked as most chosen.
- Coaches, the studio's address and facts, then a free trial form and the footer.
Design direction (use this palette only if my site has no branding):
- Near-black and white with one burnt orange accent (#c2410c in light, a brighter orange in dark), heavy condensed headings (Bahnschrift or another condensed sans), square corners.
Behaviour:
- Choosing a day or a filter updates the list and the count at once; an empty result says so and offers to clear the filters.
- Spaces left is shown as a number and a short bar; under four is marked as nearly full in words, and a full class offers the waitlist instead of Book.
- Booking a class changes its button to Booked with an undo, updates the spaces left and announces it.
- The plan switch changes prices and periods together.
- The trial form validates inline and shows 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.