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 church, mosque, synagogue, temple or other faith community site: the next service from today, the week's services, groups filtered by age, events, giving with one off or monthly and Gift Aid, and a plan a visit form, following the structure of a template I am copying.
Live template to study: https://templateinterface.com/templates/faith-community/
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/faith-community/index.html, https://templateinterface.com/templates/faith-community/styles.css and https://templateinterface.com/templates/faith-community/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, four section links, a dark or light mode button and a Plan a visit button. Below about 860px the links fold into a Menu button.
- Hero: a welcome, two buttons, three facts and the next service worked out from today.
- Services this week, with the next marked.
- Groups with age chips and a count; What's on with three dated events.
- Giving: one off or monthly, amount chips or your own amount, Gift Aid and a live summary.
- Visiting for the first time questions, a plan a visit form and the footer.
Design direction (use this palette only if my site has no branding):
- Warm stone ground, deep plum accent (#5e2a63) and soft gold for the next service.
- Book Antiqua headings, Segoe UI text, 10px corners.
Behaviour:
- The next service is found from the visitor's clock and highlighted in the week.
- Group chips filter by age and update the count.
- Giving recalculates with Gift Aid at 25% and a yearly total for monthly gifts.
- 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.