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 wiki's home page as a dense directory portal, following the structure of a wiki portal template I am copying.
Live template to study: https://templateinterface.com/templates/wiki-portal/
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/wiki-portal/index.html, https://templateinterface.com/templates/wiki-portal/styles.css and https://templateinterface.com/templates/wiki-portal/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:
- A masthead artwork across the top with the logo on it and utility controls in its top-right corner.
- A narrow navigation rail on the left carrying the whole site's structure in labelled groups.
- A thin strip of page chrome above the content: page tabs, links to related wikis, page actions (view source, history, a More menu) and search.
- Main column: welcome text beside a statistics list; a featured banner with art and an accented body.
- Featured tiles and a grid of portal tiles leading into the main areas of the wiki.
- Dense panels of dated link lists (news, recent changes, new pages, help).
- A footer.
Design direction (use this palette only if my site has no branding):
- A dusk violet theme: deep violet canvas (#241f3f), raised violet panels, lilac links (#b9aaff) and pale text (#ece9f8), with one violet accent (#7d5fe6) for fills.
- The system sans throughout, small and dense, with clear headings on each panel.
- Many small blocks rather than a few large ones.
Behaviour:
- Page tabs follow the ARIA tabs pattern. The More menu is a disclosure that closes on Escape and outside clicks.
- Search has a visible label for screen readers and a clear submit button.
- The rail collapses behind a button on narrow screens, and every link has a visible focus state.
- 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.