Claude AI website designer - UX

Looking for a web designer to assist with using Claude Code / Design I'm looking at making inner page design faster Home page I will leave the same all custom by hand But inner pages, can use Claude - See the how to here Step 1 — Design the homepage as you do now, but capture your references Keep your Awwwards ritual — that's your art direction process and it works. One change: as you browse your 30–50 sites, save the 5–8 that actually influenced the direction, with a one-line note each ("took the type scale contrast from this," "section transition logic from this"). Those screenshots + notes go in the project folder. They matter later because they tell the AI what kind of custom this project is — the difference between "custom" as a vague word and custom with a specific lineage. Step 2 — Extract the genome (30–45 min, mostly automated) Hand Claude the finished homepage (Figma link via MCP, or high-res screenshots of every section, desktop + mobile) plus your reference notes, and have it produce a Design DNA document. This is the critical artifact. It must capture two layers: The tokens (easy, mechanical): type scale and pairings, colour system, spacing rhythm, grid, corner radii, image treatment, button/link styles. The rules (this is what makes inner pages look designed): How do sections alternate — contained vs full-bleed? What's the density rhythm — where does the page breathe? How is hierarchy created — size, weight, colour, or space? How is imagery cropped and placed? What's the motion language — easing personality, what animates and what doesn't? What would this design never do? What's the signature move that makes it feel like this brand? You review and correct this document once. Ten minutes of your markup here ("no — the asymmetry is deliberate, every section offsets left") is worth ten hours of downstream fixing. This corrected doc becomes the project's CLAUDE.md. Step 3 — Build the homepage first, before designing any inner pages This is the sequencing insight most people miss. Build the homepage in code (Claude Code + Figma MCP, per the earlier workflow) before generating inner pages, because the build produces a real component library: the actual header, type components, section wrappers, cards, buttons, motion primitives. Inner pages then aren't imitations of the homepage — they're literally built from the same parts. Consistency stops being something the AI has to achieve and becomes something the system enforces. Brand drift becomes structurally impossible at the token/component level, and your quality review narrows to composition only. Step 4 — Write one-line art direction briefs per inner page (15 min, you) This is your quality lever, and it's tiny. For each page, one or two lines: About — editorial and human, image-led, slower rhythm, pull-quote moment Services — systematic and confident, tighter grid, numbered structure Case study — immersive, full-bleed hero, results as a bold typographic moment Contact — minimal, one strong gesture, no clutter Plus one rule that prevents the "template inner pages" smell: every key page gets one new bespoke element that doesn't exist on the homepage but obeys the DNA — a new layout pattern, a distinct scroll moment, a different image treatment. Homepage components alone produce pages that feel like leftovers; DNA + one fresh move per page produces pages that feel like the same designer kept designing. Step 5 — Generate inner pages in code, one at a time Claude Code builds each page from: the component library + the DNA doc + that page's one-line brief + real content (real copy matters — lorem ipsum produces lorem ipsum design decisions). Generate 2 layout variants per page where the brief allows; you pick in seconds. Step 6 — The consistency critique loop For each inner page, Claude screenshots the build and runs a structured self-check against the homepage: "Side by side, does this look like the same designer made both? Score against the DNA doc — where does it drift? Where is it too repetitive of the homepage? Does it have its one distinctive moment?" Then fixes and repeats. You review after the loop, not during it — so what reaches you is already at 8/10 and your notes are directional, not corrective. Step 7 — Your gate 15–20 minutes across all inner pages. You're curating and marking up, not designing. Corrections get written back into the DNA doc so page 6 benefits from what you fixed on page 2 — and, over multiple projects, into your standing doctrine. ____________________________________ Overall you will need to install claude code on your machine to run this and I will give you the home page design / links / info