A real case · STRATA
Every flooris a step.
Eight floors from one sentence to a live website. This tower is the course.
Hover a floor. Click one to jump straight to that step.
● Case · STRATA · screen recording of the real site
Built with Claude. Step by step.
An idea, a few references, a clear brief, and many small takes. The same route you'll follow here, step by step, with your own site.
● Rec A studio session with Marta Jakovleva
Want to build sites like this one?
Then you're exactly where you need to be. Here I'll teach you, step by step, how to build websites the way I do: with two AI tools working together. ChatGPT is your thinking partner: it helps you brainstorm, break down your references and put every task for Claude into clear, detailed words. Claude writes and builds the site, and Higgsfield AI makes the pictures. You direct; by the end your own site is live.
Independent product · not affiliated with Anthropic, OpenAI or Higgsfield · v1.5.8 beta
Step 1 Idea & concept
Find your one idea.
You describe your future website in a few short answers. Then Claude helps you make the idea sharper. Follow the steps from top to bottom.
Nothing from your previous project is kept in this workspace. Start fresh in Claude too: a new idea chat in this step, and a new Claude project in . Your old Claude project still holds the previous brief and rules.
Start fresh with a new concept, without carrying over the brief, references, or decisions from your previous project.
A short introduction · read this first
One rule for the whole course: go step by step. Everything you need is written inside each step. Read every step carefully, to the end, and do exactly what it says before you go to the next one. Don't rush and don't skip ahead: each step builds on the one before.
- Choose the kind of site you want and answer seven short questions about it.
- Copy one prompt into Claude. Claude asks you a question, then sharpens your idea.
- Paste Claude's final answer back here. That's your concept.
- A computer, with claude.ai open in another tab (Claude Pro or higher).
- About 30–45 minutes.
- A rough idea, or just the kind of site: a café, a studio, a portfolio. No design or code skills needed.
One clear idea for your website, in a single sentence, plus the answers every next step builds on.
Time, costs and what you need for the whole course are in Before you start just below. When you're ready, the project itself begins at 1.1, under Let's begin.
Before you start · 3 minutesTime, costs and what you need
You need Claude Pro or higher (Max, Ultra, Team and Enterprise work too). Pro can be billed monthly, so one month is enough to build and publish your first site.
Why not the free plan? Not because we prefer it: because of what the free plan includes. We checked claude.com/pricing on 2 November 2026. The free plan has no access to Opus, the model this course is designed for. Pro gives at least five times more usage per session than the free plan, and a full build with several rounds of changes is long: on the free plan it will most likely stop before the site is finished. Claude Code (the advanced route) and Claude in Chrome are paid-only too. That day Pro cost €18 a month billed monthly, or €15 a month billed yearly, plus tax. Prices depend on your country and change: check before you subscribe.
Rough time per step
- 01Idea
- 02References
- 03Direction
- 04Setup & Brief
- 05Build
- 06Refine
- 07Test
- 08Launch
Rough estimates for a first site. Your first time may take longer; that's normal.
What you need
- A computerLaptop or desktop for building and publishing. A phone is fine for reading along.
- Claude Pro (or higher)Needed for this course: Opus, skills with code execution switched on, and enough usage for a long build and several rounds of changes. One month is enough for your first site. Check the current price for your country on claude.com/pricing.
- PicturesHiggsfield (paid plan, every picture uses credits), another AI tool, your own photos, or placeholders for now: free.
- GitHub and Vercel accountsBoth free, needed in Step 8 to publish. You need an email address you can open. Vercel lets you sign up with your GitHub account. Vercel's free Hobby plan is for personal, non-commercial use only.
- About 1 GB free on your computerFor your site folder and pictures. Any recent browser works: Chrome, Edge, Safari or Firefox.
Plans and prices change: check claude.com/pricing and each app's own pricing page.
What you'll have at the end
- A live one-page websiteYour own idea, designed with Claude and published at a free address such as your-site.vercel.app, ready to share.
- Your filesThe site's index.html and pictures in a folder on your computer and on GitHub, plus your brief and design kit, so you can keep improving it.
- A process you can repeatThe same eight steps work for your next site.
- Not includedForms that really send, bookings and shops need an outside service: here they're built as clearly labelled demos. A custom domain (yourname.com) is optional and paid separately.
What the tools cost
- Lowest-cost routeOne month of Claude Pro, your own photos or placeholders, free GitHub and Vercel. No other subscriptions.
- Smoothest routeClaude Pro, or Max if you want longer sessions without pauses. For generated pictures, a paid Higgsfield plan: every picture uses credits. Prices depend on your country: check before you subscribe.
- A site for a businessVercel's free Hobby plan doesn't allow commercial use. A site that earns money needs a paid Vercel plan (Pro).
Pricing pages: claude.com/pricing · higgsfield.ai/pricing · vercel.com/pricing. Checked October 2026.
How every step works
- 1Fill in here
Answer the questions on this page. Your answers are written into a ready prompt for you.
- 2Copy and paste into Claude
Press Copy prompt, open Claude, paste it and send.
- 3Bring the answer back
Copy Claude's reply and paste it into the box on this page. The page takes what it needs.
Two chats, no more: Chat 1, the idea chat, for Steps 1–2; Chat 2, the build chat inside your project, from Step 5 to the end. Each step's label says which one. Don't open a new chat unless a step tells you to.
Go through the numbered steps below one by one. When you finish a step, press Mark as done (some steps tick themselves). Each step has a label that says where you do it: On this page In Claude On your computer
- On this page
Answer the seven questions
Type your answers into the fields below. They save by themselves. Not sure what to write? Press an example to see finished answers, then change them into your own. You can also use ChatGPT to brainstorm: it will help you put your answers into words.
Start here · What are you building?Choose the kind of site closest to yours. It fills this step and Step 3 with a strong starting point; then you change the words in [brackets] into your own.
Starting a new site or changing your mind? Clear all empties this step. Choosing another kind of site replaces the answers too: we ask first if you wrote them yourself.Load an example to see a finished answer:Optional. No name yet? Leave it empty: Claude suggests names in and the page fills in the one you pick.One line. Say if the brand is invented.The one action that makes the site a success.What happens to the visitor? "Every flavour has a keeper." "The camera is the visitor."Tap up to three. Tap again to remove.A section is one block of your page, about one screen as you scroll. For example: first screen → about → classes → gallery → contact. Add at least two, in the order a visitor sees them.Saved automatically in this browser only. Not synced to other devices or to Claude.
Your answers so far
ProductionYour siteStep01 · IdeaAnswered (name optional)0 / 6Name your siteOne sentence that explains everything.For who it's forVisitor should do what?Your answers save by themselves in this browser. To keep a copy (or continue on another device), use Save backup under .
When the counter on the black card says 6 / 6 (the name is optional), go to .
- On this page
Copy the prompt
Your answers are already inside this text (the underlined words). Press the yellow Copy prompt button. Nothing else to do here.
- In Claude · Chat 1 (new idea chat)
Paste the prompt into Claude and send it
- Open Claude in a new browser tab: Open claude.ai ↗ (sign in if it asks).
- Click New chat.
- Click into the message box at the bottom and paste: Cmd+V on a Mac, Ctrl+V on Windows.
- Press Enter (or the arrow button) to send.
Keep this Claude tab open. You'll come back to this same chat in .
- In Claude · Chat 1 (same chat)
Answer Claude's question
Claude tells you what's ordinary about your idea, offers three ideas and asks which one you like.
- Type the number (or letter) of the idea you like into the message box, for example 2. You can add a wish: 2, but warmer. Left the name empty? Claude also suggests three names: add the one you like, e.g. 2, name B.
- Send it.
- Claude replies with a short final version. It has a line that starts with IDEA: and a line that starts with SECTIONS: (and NAME: if you asked for a name).
- On this page
Paste Claude's final answer here
- In Claude, under its last reply, press the Copy button (an icon of two small squares). Or select the text with your mouse and press Cmd+C / Ctrl+C.
- Come back to this page, click into the box below and paste (Cmd+V / Ctrl+V).
- Press Use this answer. The page finds the IDEA and SECTIONS lines and puts them into questions 5 and 7 for you. The OFFER line goes to : the sentence your first screen must say.
How three of Marta's sites startedtap to compare
Step 2 Visual research
Take the grammar, not the design.
A reference is a website you like: its mood, fonts, the way it moves. You show 3–5 of them to Claude so it understands your taste. You borrow the idea, never copy the design.
- In your browser
Find 3–5 websites you like
Your references become Claude's guideline: choose them carefully. Claude builds the look of your whole site from the references you give it. Their mood, fonts, layout and movement become the base for every section. Random or weak references give a weak site; well-chosen references with clear notes give the site you have in mind. So for each one you'll say exactly what you want to take from it and what to leave out.
Give Claude more than pictures. The more Claude sees, the closer it gets to the site you have in mind. For each reference you can add:
- A screenshotThe look: colours, fonts, layout, empty space.
- A short screen recordingThe movement: a scroll effect, a fly-through, a hover. The board turns it into four frames for Claude.
- The live linkClaude opens the page and reads how it's built. It can't watch it move: that's what the recording is for.
Then say in words what to repeat: "the same fly-through from room to room", "this stepped scroll, one screen per swipe", "the product assembles as you scroll". Claude rebuilds that kind of interaction for your own site, with your content and pictures.
Your references decide how your finished site will look. Take your time choosing them.
Found a site with a ready concept you love? Use it. For example, an Awwwards site where the camera flies from room to room, or where the product is assembled as you scroll. Add that site as a reference and write in Principle to borrow: "Repeat this site's concept: [what happens, in your words]". Claude studies how the idea is built and makes the same kind of presentation for your site, with your content, pictures and colours. Add a short screen recording too: Claude can read a link, but it can't see the movement on it.
Let ChatGPT break down your references. Show it your screenshots and ask: what makes this work, and which direction should I give Claude? It's very good at reading a reference and explaining it in detail. Put its best points, in short lines, into Principle to borrow and Avoid.
Open these galleries in a new tab and browse. When a site makes you stop and think "I want that feeling", it's a reference. Take at least one from outside your own category (a hotel site can borrow from a film title or a museum): three sites like yours only teach you what everyone already does.
How a designer reads a reference: seven lenses
- Composition: where things sit, how much empty space there is
- Hierarchy: what you see first, second, third
- Typography: the display font against the text font, and the size contrast between them
- Transitions: how one section hands over to the next
- Interaction: what you can touch, drag or click, and what answers
- Motion: what moves, what starts it, how fast, how it slows down
- Emotional effect: what you feel, and which of the above causes it
Adapt, don't copy. Write down the principle, not the look: not "black background with a gold serif", but "one huge image per screen, and the text waits until the image has settled". Then make it yours with your idea, your material and your palette. Colours, logos, texts and exact layouts stay with their owner.
Where to find them: Awwwards ↗Siteinspire ↗Pinterest ↗Dribbble ↗Behance ↗
- On your computer
Take a screenshot of the part you like
For each reference, take one screenshot of the part you like. Remember where the file is saved: you'll need it twice.
MacCmd+Shift+4, then drag over the area. The file lands on your Desktop.WindowsWin+Shift+S, drag over the area. It's copied; you can paste it straight onto the board here.iPhonePress the side button and volume up together. It's saved in Photos.AndroidUsually power and volume down together. It's saved in your gallery.The thing you like moves? Record a short video instead
For a scroll effect, an animation or a hover, a screenshot can't show the movement. Record 5–20 seconds of the screen instead:
MacCmd+Shift+5 → Record Selected Portion → Record. Stop with the ■ button in the menu bar. The video lands on your Desktop.WindowsOpen the Snipping Tool, switch to the video camera icon, press New, drag over the area, record, stop.iPhoneControl Centre → the Screen Recording button (●). Stop it with the red pill at the top.AndroidQuick settings → Screen record.On the board you add the video the same way as a screenshot. The page takes four still frames from it and keeps those, not the video: Claude's chat accepts pictures, but video files aren't on its list of supported uploads. So you also describe the movement in words.
No video, or the page can't open yours? Take 2–4 screenshots of the movement at different moments (pause the video, or scroll the site a little between shots). Select them all together and drop them on the board at once: they become one frames picture, in the order of their file names.
- On this page
Put each reference on your board
The board is your notebook: it keeps your references and writes the next prompt for you. Claude can't see it. For each reference:
- Click the box Add a screenshot or video and choose your file (on Windows you can also paste a screenshot). A video becomes four still frames. Several screenshots chosen together become one frames picture.
- In the website's tab, click the address bar at the top, copy the address (Cmd/Ctrl+C) and paste it into Link.
- Write one line in Principle to borrow: the idea underneath, not the look (see the seven lenses in ). For a video, describe the movement, e.g. "the photo zooms in slowly as you scroll". Be specific: Claude follows this line.
- Write in Avoid what you don't want from this site, e.g. "their colours, the dark mode, the busy menu". Without it Claude may take everything, including what you don't like.
- Press Add to board. A card appears below. Repeat for each reference.
Saved in this browser onlyYour reference board
0 references+Add a screenshot or videoClick to choose · drag a file here · or paste (Ctrl/Cmd + V)Links and notes are saved in this browser. Screenshots and video frames are kept in this browser's storage. Videos themselves are not stored.
When you have 3–5 cards on the board, go to .
- On this page
Copy the prompt
This text already lists every reference from your board. Press Copy prompt.
- In Claude · Chat 1 (same chat as Step 1)
Send the screenshots and the prompt to Claude
Go back to the Claude tab from . Everything happens in one message:
- Click the + button in the message box → Add files or photos.
- Choose the same screenshot files from your computer. For a video reference, attach its frames picture (press Download frames on its card first), not the video. Small previews appear in the message box.
- Click into the message box and paste the prompt (Cmd/Ctrl+V).
- Send.
Pasted a screenshot straight onto the board and don't have the file? Press Download screenshot on its card, then attach that file.
- On this page
Paste Claude's answer here
- When Claude has finished, press the Copy button under its reply.
- Click into the box below and paste. You can paste the whole reply: the page keeps only the part called BORROW / AVOID and adds it to your brief.
Paste Claude's whole reply. The page keeps only the BORROW / AVOID part and puts it into your brief.
Claude says it can't open my link
Claude can sometimes read a page's text from a link (when web search is available), but that's text, not how the page looks. For design, always attach a screenshot. If a site later goes offline, your screenshot is still there.
Vesper · what a 20-second reference becamedrag to walk in
Step 3 Creative direction & structure
Decide how it looks and moves.
Before Claude builds anything, you decide the look, what moves, what goes into each section and what must work. Your references from help. Everything you choose here goes into your brief in .
- On this page
Describe the look
Look at your references, then choose from the suggestions below: tap one or two in every group (Mood, Colour, Fonts, Light and texture, Pictures). Each tap adds the words to the box. Afterwards, change them so they sound like you.
Your BORROW / AVOID notes fromColours, fonts, light, mood.How expensive should it feel? Every picture prompt carries this.The overall light of the pages and the pictures. - On this page
Design your signature moment
Strong sites have one signature moment: the thing people remember and show their friends. You don't ask Claude for "animations"; you direct the moment like a short film scene: what is on screen, what starts it, what happens first, next and last, how long it takes and how it moves. The signature moment leads; around it, every section still moves in the same style, as much as you choose in point 5. You can also use ChatGPT to brainstorm: it will help you find and describe your moment.
- Pick the pattern that carries your idea best. Open About this pattern to see what makes it feel cheap and how to check it.
- The fields below fill with a strong starting point. Change them so they describe your site.
- Can't decide between two ideas for the moment? Describe the one you like most here. In the build chat Claude can first make 2–3 small versions of it to choose from: just ask Before the full build, show me 2–3 versions of the signature moment, each in its own file.
- Write the whole moment in one sentence at the end. Want to see this level of direction in a real project? See below the steps.
What does the visitor do, and what happens? This sentence leads your brief.Claude adds more from the motion library in the same style; pick the ones that matter to you.The signature moment leads either way. This decides how much every other section moves.Short videos made from your own pictures. A fly-through is the most immersive: the camera travels through your spaces as the visitor scrolls.Decide it now: in a test build this came up only after the site was finished, and cost five rounds. - On this page
Say what it is, then plan the content
First write, in plain words, what your site offers: a visitor who doesn't get it in five seconds leaves, however beautiful the motion. Then decide where the texts and pictures come from. You don't need to have anything yet: Claude can write the texts, and Higgsfield AI can make the pictures.
One sentence a stranger understands in five seconds: what this is, who it's for and what they get. No metaphors here: your idea and your signature moment come on top of it, they don't replace it. The idea chat suggests one (its OFFER line).The plain facts your sections explain: what's included, how it works, how long, how much, where, when. Not decided yet? Write your best guess with [CHECK]: Claude lists these for you to confirm and never shows the mark on your site.Which tool will you use?
- On this page
Decide what must work
Pick the things a visitor must be able to do. Then choose how the site is built. Start simple unless your signature moment really needs more: you can move to the advanced route later with the same brief.
A form that really sends email, a booking system or a shop needs an outside service. For a first version, ask for a clearly labelled demo.
Flagship case · STRATA, from idea to liveMarta's own project
One idea, directed all the way: "moving through architecture"
STRATA is a concept site for a fictional residential building in Riga. Here is how its concept, direction, motion, build and testing connect. Every point is labelled: Documented means STRATA's own case study or README says it; From the code means it's read from STRATA's source code; Recommendation is new advice for you. No original prompts from STRATA were saved, so this case shows none.
- Documented "STRATA is not a gallery of renders. The whole site is built around one idea — moving through architecture."
- Documented "Every transition is a camera move inside one space — never a page change."
- Recommendation Write your idea as a rule that decides later choices for you. "Never a page change" ruled out modals, page loads and hard cuts before any design existed.
- Documented Imagery: "AI-generated with Higgsfield, art-directed".
- From the project files One master photograph of the building (2688 × 1520 px), plus 26 stills: a facade close-up for each floor, interiors per floor, materials, a detail and the landscape.
- From the code Each floor has its own hour and light, e.g. the ground floor at 18:20 in evening lamplight, floor 01 at 07:40 in morning mist.
- From the code Materials became the palette: basalt , travertine , bronze , birch .
- From the code Three typefaces with clear roles: Instrument Serif (display), Hanken Grotesk (text), IBM Plex Mono (labels).
- Recommendation Generate one master picture first and derive the rest from it, so light and material stay consistent.
Six moves, each specified with a name, a from → to, a duration and one sentence. This is the precision your motion spec in aims for. Documented
- From the code The opening assembly: each floor slab is lowered 70 px over 1.15 s, the next starts 0.36 s later, eased so it "stops dead on its seat" with no bounce, sharpening from a 5 px blur.
- From the code Stepped scenes: "scroll chooses the direction, never the speed". One gesture moves one state through a transition of fixed length, so fast flicks can't skip anything.
- From the code On phones the camera push-in is a pure function of scroll progress: every scroll position has exactly one camera, so nothing lags or jumps.
- Recommendation Give every move a name and a one-line purpose. If you can't say what a move is for, cut it.
- Documented Stack: React · GSAP · Lenis · Vite · Vercel. This is the advanced route, chosen because one camera engine drives every move.
- From the code One "Director" owns every camera move; a separate camera module does the framing maths. The motion lives in one place instead of being spread across the page.
- From the code All content (floors, specs, prices, plans) sits in one data file, separate from the motion code, so texts change without touching animation.
- Recommendation On the simple route, ask Claude for the same separation inside one file: all texts together at the top, and durations and easings as named values you can tweak.
- From the code Reduced motion is respected: smooth scrolling switches off and held scenes move faster.
- From the code On phones the camera frames the stage, not the window, so the browser's address bar showing or hiding can't shift the picture.
- Documented The case study judges the interface with close-ups "cropped from the recordings": the moves were screen-recorded and examined.
- Documented Published on Vercel: strata-residences-mu.vercel.app ↗.
- Recommendation Screen-record your signature moment and watch it slowly. Jumps, stutters and late text are easy to miss live and obvious on a recording.
What Claude sends back after the brief · from Marta's projects
Odd Orchard · one master bottle, then every flavour generated from it
Step 4 Claude setup & project brief
Set up Claude, hand over the brief.
You create a project in Claude: a folder for your website that keeps your rules and your brief, so every chat starts informed. If you'll generate your pictures, you also connect Higgsfield AI to Claude. Then you check your brief, put it inside, and add a small design kit: two files and a few skills that keep Claude's design consistent from the first build to the last fix. You do this once. No software to install: Claude in the browser is enough.
- In Claude
Turn on file creation
- In Claude, open Settings (in the menu under your name).
- Open Capabilities.
- Switch on Code execution and file creation (in some versions it's called Create and edit files). It's usually on already. Claude needs it to make files you can download. On a work (Team or Enterprise) account your admin controls this switch.
Can't find it? Menus change sometimes. Search "code execution" at support.claude.com.
- On higgsfield.ai
Get a Higgsfield account (for your pictures)
Claude writes your texts and builds the site, but it can't make photos by itself. Higgsfield AI generates images and short videos. Once it's connected to Claude (next step), Claude can ask it for exactly the pictures your site needs, in your style.
- Open higgsfield.ai ↗ and sign up, or log in if you already have an account.
- Look at the plans on its pricing page. Higgsfield's help centre says that using it from Claude needs an active paid subscription, and every picture made through Claude uses credits.
- Stay logged in in this browser: in the next step you sign in through it.
You'll never paste a Higgsfield password or key into Claude. The connection uses Higgsfield's own sign-in window.
- In Claude · connectors
Connect Higgsfield to Claude
A connector lets Claude use another app for you. You add it once; it then works in every chat where it's switched on.
- In Claude, open Customize → Connectors. (In some versions it's Settings → Connectors.)
- Click + Add → Add custom connector.
- Name: Higgsfield. In the URL field paste this address:
https://mcp.higgsfield.ai/mcp
- Click Continue until you see Add, then click Add. When Higgsfield asks you to sign in (sometimes after a Connect button), sign in and allow access. Already logged in at higgsfield.ai? It happens by itself.
- Check it: start a new chat, click + → Connectors and make sure Higgsfield is switched on. Ask: What is my Higgsfield credit balance? If Claude answers with your balance from Higgsfield, it works.
Higgsfield itself needs a paid Higgsfield plan whatever your Claude plan; on a tight budget, use your own photos or placeholders instead. Using a work (Team or Enterprise) account? An admin adds it under Organization settings → Connectors; then you find it under Connectors and press Connect.
- In Claude
Create a project for your site
- In the left sidebar of Claude, click Projects.
- Click the button to create a new project.
- Name it after your site and create it. Leave the second box (What are you trying to achieve?) empty: your rules go in later. You land on the project page.
Building another site? Create a new project for it. Don't reuse the old one: its files and instructions belong to your previous site, and Claude would mix the two.
- On this page
Copy the project rules
These are standing rules Claude will follow in every chat of your project. Press Copy prompt.
- In Claude · your project page
Paste the rules into the project's instructions
- On your project page, find Set project instructions (or Instructions) and click it.
- Paste (Cmd/Ctrl+V).
- Press Save. Claude doesn't reply to this: it just remembers.
Leave the project page open. In you'll add your brief to it.
- On this page
Check your brief
This is the document Claude will build from. It was written from your answers in Steps 1–3. The ring shows how complete it is: each "Missing" word is a button that takes you to that field. Orange [MISSING] marks are fine: Claude will ask about them. Want to change a word? Press Edit the text.
0of 11Brief sections filledMissing: …
Brief · generated from your answersYou're using your edited version. Changes in the fields won't update it. - On this page
Download the brief
Press Download brief. A file named my-site-brief.md lands in your Downloads folder.
Downloading inside Claude? Claude asks Allow this artifact to download a file?: press Save file. One file at a time.
- In Claude · your project page
Add the brief to your project
- Open your project in Claude (Projects → your site).
- On the project page, find the files area on the right (it may be called Files, Project knowledge or Context) and add the file.
- Choose my-site-brief.md from your Downloads folder.
Now every chat in this project can read your brief. You'll never paste it again.
- On this page
Your design kit for Claude
A brief says what to build. A kit makes Claude build it the same disciplined way every time: a design system file with your exact colours, type, spacing and motion rules, a decisions file with what you've agreed, small skills that each do one job, and an independent reviewer that checks the result without seeing your build chat, so it gives no allowances for what you discussed. This page writes the whole kit from your answers; you only add it to Claude in the next step.
Recommended for your site
New to this? Leave the ticks as they are. They're already set for your site from your answers in Step 3. Change them only if you know you need something else.
File, skill or reviewer: what's the difference?
Files (design-system.md, decisions.md) live in your project, next to the brief. Every chat in the project can read them, and they only describe this site.
Skills are short instruction folders Claude loads by itself when a task matches, for example "build this section". In the browser they belong to your whole Claude account, not to one project, so the kit's skills hold no details of your site: they always read the design system and decisions of the project you're working in. That keeps one site from leaking into another.
The reviewer must not know your build chat. On the simple route that's simply a new chat in your project (Step 6); on the Claude Code route it's an agent file, which Claude Code runs in its own separate context.
Checked 2 November 2026: skills need code execution switched on (Claude's help centre). Pro includes skills and code execution.
- In Claude · your project + Customize
Add the kit to Claude
- Two files into your project. Download them, then on your project page click + in the files area and add both, the same way as your brief. Built a site with this course before? Your Downloads may already hold a design-system.md from it, and the new file then arrives as design-system (1).md. Take the newest one and check its first line names this site (your site); move the old files out of Downloads first and it can't happen.
- The skills. Don't skip this one: the skills are what make your site immersive. Without them Claude falls back on its generic habits: plain fades, a still first screen, a page that looks like every other AI-made site. Each skill is a tested recipe for one job:
- design-foundations (required for every site) sets the premium basics the others build on: fonts and sizes, one accent colour, even spacing, the header and menu, the footer and the buttons.
- make-section builds every section the same careful way, with your colours, fonts and spacing.
- make-mobile makes each section look and work right on a phone.
- motion-plan decides one style of movement for the whole site before the build starts.
- motion-library and motion-pass give every section and transition designed movement instead of a plain fade.
- hero-moment makes the first screen arrive with impact.
- scroll-story builds the effects that move with your scroll.
- scroll-film builds a fly-through from stills and video clips.
- real-photo keeps AI pictures looking like real photographs.
- frontend-design, Anthropic's design skill. In Customize → Skills type frontend-design in the search box. In the current Claude it comes from Anthropic as a plugin: if you see Add next to it, click it and it switches on by itself. If it's already in your list, make sure it's switched on. Only if you can't find it at all, download it here and upload it like the others. Two copies of the same skill only create confusion.
- The reviewer. Nothing to install. In you open a new chat in this project and paste the review prompt.
Second site? Skills you uploaded for an earlier site are already in your account and work for this one too: don't upload them again. Add only the two new files to the new project.
Only add skills from sources you trust: a skill tells Claude what to do. The kit's skills are plain text: open the .zip and read them if you like.
- Download the kit (one .zip):
- Unzip it into your site folder my-site, so CLAUDE.md sits at the top level of the folder. Put your brief file (my-site-brief.md) there too. Folders starting with a dot are hidden: on a Mac press Cmd+Shift+. in Finder; on Windows choose View → Show → Hidden items.
- Already have a CLAUDE.md in that folder? Keep yours and paste the kit's text at the end of it.
- frontend-design, Anthropic's design skill. In Claude Code type these two commands, one after the other. The second one installs Anthropic's example skills, frontend-design among them.
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills
Commands from the README of github.com/anthropics/skills, October 2026.
- Two files into your project. Download them, then on your project page click + in the files area and add both, the same way as your brief. Built a site with this course before? Your Downloads may already hold a design-system.md from it, and the new file then arrives as design-system (1).md. Take the newest one and check its first line names this site (your site); move the old files out of Downloads first and it can't happen.
- In Claude · new chat in your project
Check that Claude sees the kit
Open a new chat inside your projectStart Claude Code in your site folder, paste the check prompt, send, and paste Claude's whole reply below. This page compares it with your kit.
What this proves: that Claude reports it can see the files and skills. Whether they make the design better shows in , when the reviewer checks your site against them.
Which Claude do I need? Browser, app or Claude Code
Which Claude do I need?you need only the firstyour route: the first and Claude Code
claude.ai. Nothing to install. Projects, previews and file downloads all work here.
Needs Claude Pro or higher (see Before you start). Long builds use a lot of your usage: if you reach a limit, wait for the reset and continue in the same chat.The same chat in its own window. Download from claude.ai/download ↗.
Not required for this course.A coding assistant that works in a folder on your computer and can run a live local preview. For bigger sites.
Needs a paid plan: Pro, Max, Ultra, Team or Enterprise. Official setup ↗. Skip it for now.You use it from Step 5 on.Skills: what they are
A skill is a small folder of instructions Claude loads by itself when a task matches its description. Your kit in brings the skills this course uses, written so they read your project's design system instead of holding details of one site. Anthropic also publishes example skills at github.com/anthropics/skills ↗. Menu names from Claude's help centre ↗, checked October 2026.
Your Claude project, three layerstap each layer
Project
A workspace for one site
Knowledge
Your brief, references, screenshots
Rules
Project instructions
Illustration, not a real screen. Menu names in Claude can change.
Step 5 Build the whole site
Watch it come alive.
This is the main step. One prompt carries everything you decided: the structure, the look, your signature moment and its motion, where the pictures come from and who writes the texts. Claude plans in a few lines, makes the pictures and builds the whole interactive site in one go. You open it on your computer with every animation working, and refine it in Step 6.
- Your computer + Claude
Get ready: your site folder and the build chat
- On your Desktop make a folder called my-site, and inside it a folder called images. (Mac: right-click the Desktop → New Folder. Windows: right-click → New → Folder.) Your site will live here.
- In Claude open your project (Projects → your site) and start a new chat from the project page, so it sits inside the project.
- In that chat click + → Connectors and check that Higgsfield is switched on. Claude needs it to make your pictures.
This is Chat 2, your build chat. You'll use this same chat until the end of the course. Chat 1 (the idea chat from Steps 1–2) has done its job.
Advanced route: instead of a chat, open the my-site folder in Claude Code (desktop app → Code → Local → Select folder) and use the build prompt there. If Claude Code can't reach your picture connector, it will say so: then make the pictures in the build chat with the extra picture prompt from the Prompt kit.
Your folder now
📁 my-site📁 images empty for now - On this page
Copy the build prompt
One prompt instead of separate plan, picture and build prompts. Check what's inside first: anything marked missing is worth filling in before you copy, because Claude can only build what you decided.
- In Claude · Chat 2 (build chat)
Attach, paste, send
Before you send, check the model. Look at the bottom of the message box: it shows which model Claude will use. Choose Opus 5.5 and set it to High. We recommend it for this build: it gives you the best chance of a site that really stands out. It uses up your plan's usage faster, but this is the message where quality matters most.
- In the build chat click + → Add files or photos and choose your reference screenshots from Step 2. Add your own photos too. Give them simple lowercase names first, like hero.jpg or studio-1.jpg.
- Paste the build prompt into the same message and send. A long prompt turns into a small card above the box (PASTED): that's normal, Claude reads all of it.
- Claude starts with a short plan: the idea, the sections, your signature moment second by second, colours and fonts, and the list of pictures. Then it carries on by itself. It stops only where the next points say: once for the credits (if you chose to approve them) and once for the mood check.
- Then it shows the picture list with the credits and asks once. Reply OK. Want fewer pictures? Say it now, e.g. Only five pictures, skip the gallery.
- Right after the plan come the picture prompts for your tool, one per picture. You use them in the next step.
Claude asks you for texts? Reply: Write them yourself from my brief. It stops after the plan? Reply: Go on: build the whole site now, as the build prompt says.
- Claude + your computer
Your pictures
Claude makes the pictures itself with Higgsfield: the MASTER first, then the others in the same light and style. You don't need to download anything yet. Claude puts each picture into the site by its link, and at the end gives you a list to save them into images ().
Don't like a picture? Wait until the site is built, then ask for that one change in Step 6, e.g. hero picture: warmer light, more empty space on the left for the heading. Each new try uses credits.
- While Claude builds, open your tool and generate the pictures from Claude's prompts: the MASTER first, then the others, using the master as a reference image if the tool allows it.
- Download each picture and move it into images, renamed to exactly the file name in its prompt. Keep the real ending (.jpg, .png or .webp); if it differs from the prompt, tell Claude the real name.
- Until a picture is there, the site shows a calm colour field with the file name. Put the file in, reload the page, and it appears.
Copy the same photos you attached into images, with exactly the same names. That's how the site finds them on your computer.
Copy your own photos into images with the same names you attached them with. The rest Claude makes with Higgsfield and puts into the site by their links; you save those from its list in .
Nothing to do now. The site uses designed colour fields with the file names. Add real pictures any time: put a file with that name into images and reload.
You haven't chosen where your pictures come from. Choose it in , then copy the build prompt again.
- In Claude · Chat 2 (build chat)
Let Claude build the whole site
- Claude now writes the whole site. It takes a few minutes, longer with pictures. Leave the chat open and don't send anything in between, except your answer to the mood check below.
- Before you see anything, Claude checks its own work. It looks at the whole site on a laptop and a phone against your wow card and fixes what falls short. This takes longer and uses more of your Claude limit; it's what makes the first version worth showing.
- One stop on the way: the mood check. Claude shows the main picture, two more, the colours and the first screen. Answer OK, or say what feels wrong (too dark, too rustic, not premium enough). Changing the mood now costs minutes; after the whole build it costs a new site.
- If it stops in the middle or writes CONTINUE, type continue. It goes on exactly where it stopped.
- If Claude says you've reached your usage limit, nothing is lost. Wait until the limit resets (Claude shows when), then open the same chat and type continue.
- At the end you get index.html, a list of your pictures with their links, three lines on what to try first, and what Claude checked and couldn't check.
- Claude's own preview may not show the pictures or every animation: it runs in a closed box and can't see your folder. The real test is the file on your computer, in the next step.
Edits are what make the site good: don't skip them. Claude can't know how you picture each detail, so its first draft is a starting point, not the result. As soon as you see the mood check or the first screen, tell Claude right here in the chat, typed or by voice, exactly what to change. For example: "The table looks worn, and this is a premium site: make it look polished and expensive." "Show the jewellery large, with beautiful light on it, like in this reference." Fix it now: whatever you let through at the start carries into every section after it. Attach a reference again whenever it helps, and say exactly what you like in it (the light, the size, the layout) and how to use it on your site. Ask for as many rounds of edits as you need. Not sure how to put an edit into words? Describe it to ChatGPT and ask it to write a precise instruction for Claude. Without edits the site stays flat; with them it becomes yours.
- Chat 2 + your computer
Save it and open your whole site
- In Claude click the index.html file and download it. No download button? Write: Give me the complete index.html as a file to download. Download each file on its own: Download all may save only the first one.
- Find it in your Downloads folder and drag it into my-site on your Desktop, next to images (not inside it). It arrived as index (1).html? You already had an index.html in Downloads: take the newest one and rename it to exactly index.html in your site folder.
- Save the pictures: open each link from Claude's list, download the picture and move it into images, renamed to the file name in the list. While you're online the site already shows them through the links; saved in your folder, they also work offline and when you publish in Step 8.
- Double-click index.html. Your whole site opens in the browser. 🎉
- Walk through it slowly: does the signature moment work within 3 seconds? Are all your sections there, in the order of your brief? Does every picture show? Make the window narrow to see the phone version.
- Something's off? Don't fix it here. Write it down: Step 6 turns your notes into precise rounds of changes.
Your fly-through: from clips to frames
Scrolling a video backwards stutters; scrolling numbered pictures doesn't. This tool turns your fly-through clips into pictures, right here in this page. Nothing is uploaded.
- Save every fly-through clip from Claude's list into your Downloads (open the link, then save the video). Keep Claude's names: they start 01-, 02-… and the order matters.
- Choose them all here at once. Keep this tab in front while it works (about 10–20 seconds a clip). Chrome or Edge make the smallest files.
- Save the zip, unzip it into your images folder: you get images/film/ with a folder per clip and manifest.js.
- Copy the message below into the build chat, so Claude switches the site from the clips to the frames.
No clips chosen yet.
Grey boxes or empty spots? Open the file from your folder, not Claude's preview. Still missing: compare the names in images with Claude's list (capital letters and .jpg / .png count) and tell Claude the real names.
Your folder
📁 my-site📄 index.html📁 images your pictures, named as in Claude's list
What happens now
From here on, your site grows in conversation.
The first version is a starting point, not the result. Everything after this happens in the same build chat (Chat 2): you talk to Claude like to your own studio partner, until the site looks the way you see it.
Want a second pair of eyes or fresh ideas? ChatGPT can review your site or brainstorm with you (). Claude stays the one who changes the file: you bring the best points back to it. Step 6 shows a method that keeps every change under control.
A finished build · Odd Orchard · switch the worldreal screenshots
The images it was built from: one master bottle, every flavour generated from it
Generate one master image, approve it, then make every other image from it. That's why my four bottles look like one product line.
Marta · Odd OrchardStep 6 Refine & iterate
Take two. Take three.
Now you shape the site until it matches what you see in your head. Everything happens in your build chat: you can talk to Claude freely, give it tasks, attach screenshots and new references, and bring ideas, your own or ChatGPT's. This stage is about how it looks and feels; whether it works is checked in Step 7. The method below keeps you in control: Claude critiques first without changing anything, then you fix one problem per round and check that nothing else broke.
- In Claude · Chat 2 (build chat)
Creative review: Claude critiques, you decide
Claude looks at the site like a strict art director and names the three problems that matter most, without changing anything. You stay the director: you check each problem with your own eyes in the next step and choose what to fix. Changing many things at once makes it impossible to see what helped and what broke. Press Copy prompt, paste it into Chat 2 and send.
- In your browser + this page
Look at your site and tick what's true
Open your site (double-click index.html). Go through the list and tick everything that's true. Anything you can't tick is a problem to fix.
- In Claude · Chat 3 (review chat)
Independent design check
Your build chat knows everything you discussed, so its own reviews go easy on what you "meant". A reviewer that hasn't seen that chat judges only what's really in the site, against your design system and decisions.
- Open your project in Claude → New chat. This is Chat 3, the review chat. Don't use the build chat for this.
- Attach your latest index.html and two or three screenshots: the first screen on a laptop and on a narrow window.
- Paste the prompt and send. Claude changes nothing; it returns a table and a FIX LIST.
- Take the FIX LIST lines you agree with into , or paste them into the build chat one at a time.
- In Claude Code in your site folder, paste the prompt. It runs the design-review agent from your kit, which works in its own context.
- Take the FIX LIST lines you agree with into .
- In ChatGPT · recommended
A second opinion and ideas from ChatGPT
Two AIs see more than one. ChatGPT can review your site with fresh eyes or brainstorm ideas with you. Claude stays the one who changes the file: you bring ChatGPT's best points back into the build chat. Two tools editing the same code is how sites break.
- Open chatgpt.com ↗ and start a new chat.
- Attach what it should look at: screenshots of your site (desktop and a narrow window), and if your plan allows it, a short screen recording of your signature moment or the index.html file. From the code alone it can't feel the motion, so screenshots help most.
- Paste one of the two prompts below and send.
- Read the answer like a director: take only what fits your idea. Paste the chosen points into the build chat one at a time, or turn them into notes in .
Prompt 1 · a second opinion on your site
Prompt 2 · ideas to make it more memorable
Don't paste code from ChatGPT into your site. Ask it for short instructions instead and give those to Claude. And never share passwords, keys or private data in either chat.
- On this page
Describe each problem
- Press Write a note next to a problem above, or pick a problem type below.
- The fields fill with a starting text. Replace the words in [brackets] with what you see.
- Press Add to this round. Start with one problem: the one that matters most. Up to three per round are possible, but one at a time shows clearly what helped and what broke.
Correction builder
What's wrong?0 / 3 notes - On this page
Copy the round prompt
This text is built from your notes. Press Copy prompt.
- In Claude · Chat 2 (build chat)
Paste it into the build chat and send
- Go to your build chat from .
- Have a screenshot of the problem? Attach it: + → Add files or photos. Attach a reference again too, and say in one or two sentences what exactly to take from it and how to use it here.
- Paste the prompt and send. Claude makes a new index.html. Not right yet? Say so in the same chat and keep going: as many rounds as you need.
- On your computer
Replace the file and check again
- Keep the old version first: in your folder, rename the old index.html to index-v1.html (next time v2, v3…). Then put the new index.html next to it. If the new one breaks something, delete it and rename the old one back to index.html.
- Download the new index.html and put it into your folder.
- Open the old and the new version in two browser tabs and compare: is the problem fixed? Did anything else change? Check the signature moment, the menu and a narrow window.
- Quick regression check: the signature moment, the menu, every button you touched, and a narrow window. Something broke? Restore the old version (above) and tell Claude what broke.
- Press Clear this round in . Still not happy? Start the next round at : one problem at a time. Happy with how it looks? Go to , where you check that it works.
Real notes from Vesper and STRATAvague → precise
Step 7 Test & fix
Test it like a stranger.
Before the world sees it, Claude runs your site like a visitor (four screen sizes, scrolling down to the end and back with a wheel, a trackpad, keys and a finger, the console, the smoothness) and fixes what fails. Then you check it with your own hands. "Done" in a chat isn't proof: opening the site is.
- On this page
Copy the final audit prompt
- In Claude · Chat 2 (build chat)
Attach your latest index.html, paste, send
- In the build chat click + → Add files or photos and choose index.html from your folder.
- Paste the prompt in the same message and send.
- Claude answers with a table and a fixed file. Download it and replace the old one in your folder.
- In your browser + this page
Check it yourself, point by point
Open your site and tick each point only when you've checked it yourself. Something fails? Go back to and fix it in a new round.
0of 9
How the finished sites look in a handswipe →
Step 8 Deploy & launch
Put it on the internet.
Your folder goes to GitHub (it stores your files), and Vercel turns it into a real website with its own address. Everything happens in the browser. Free accounts are enough for a personal site.
- On this page
Copy the last check
- In Claude · Chat 2 (build chat)
Send it with your files, fix what it finds
- Attach index.html (and your images, if you have any) with + → Add files or photos.
- Paste the prompt, send.
- Anything marked "Fix needed"? Ask Claude to fix it, download the new file, replace the old one.
- On github.com
Create a free GitHub account
- Open github.com/signup ↗.
- Sign up with an email you check and confirm it.
- On github.com
Create a repository (an online folder)
- Top right, click + → New repository.
- Name it my-site. Public or Private are both free.
- Click Create repository.
- On github.com
Upload your files
- On the new repository page click uploading an existing file (or Add file → Upload files).
- Open your my-site folder on your computer, select everything inside it (index.html and the images folder, if any) and drag it onto the page.
- Click the green button at the bottom of the page (usually Commit changes). GitHub calls saving a commit.
index.html must be at the top, not inside another folder. Limits: 25 MB per file, 100 files at a time. More than 100 files (a fly-through has about 60 frames per clip)? Upload in rounds: first index.html and the images folder with only the first clip's folder inside images/film; then, in your repository, open images → film, choose Add file → Upload files, and drag in the next clip's folder. Repeat for each clip. GitHub's guide ↗
- On vercel.com
Sign up at Vercel with GitHub
- Open vercel.com/signup ↗.
- Choose Hobby (free, for personal non-commercial sites) and Continue with GitHub.
- GitHub asks for permission: read it and approve it yourself.
Building a site for a paying client? Vercel's rules require the paid Pro plan for commercial use.
- On vercel.com
Import your repository and press Deploy
- On your Vercel dashboard click New Project (it may be inside an Add New… menu).
- Find your repository in the list and click Import. Not listed? Follow Vercel's prompt to give it access.
- Framework Preset: Other. Leave the rest as it is and press Deploy.Framework Preset: Vercel usually detects Vite by itself; if it doesn't, choose Vite. Keep the suggested build settings and press Deploy.
- Wait until it's ready. Vercel shows your address ending in .vercel.app.
Build error? Turn on Override next to Build Command, leave it empty, deploy again.
Build error? Open the build log, copy the red lines and paste them to Claude Code in your site folder. Fix, push, and Vercel deploys again.
- Your phone + this page
Open it on your phone and save the address
- Open the .vercel.app address on your phone, using mobile data.
- Copy it and paste it into the field below.
Later, to change the site: upload the new files to GitHub the same way. Vercel updates the site by itself.
Understand GitHub and Vercel · fixes when something goes wrong
Three places, one directiontap each place
Accounts and plans
GitHub Free includes unlimited public and private repositories. Uploads in the browser: up to 25 MB per file, 100 files at a time.
Vercel Hobby is free, but only for personal, non-commercial use. If you're paid to build or host the site, or it shows ads, Vercel requires the Pro plan. Hobby plan ↗
Keep the repository in your personal GitHub account: Vercel's free plan can't deploy private repositories that belong to a GitHub organization.
When something goes wrongcopy the matching prompt
Live right now, built this way
● That's a wrap
Your site is live.
Here's everything you did, checked against what you saved. Anything still open links back to its step.
Show it
Your site deserves an audience.
- Record 20–30 seconds of your signature moment, scrolling slowly. Mac: Cmd + Shift + 5 → Record Selected Portion. Windows 11: Snipping Tool → Record.
- Paste the case study prompt into your build chat: Claude writes a Behance-style case from your brief, ready to lay out with your screenshots.
- Paste the post prompt: a caption and a short reel plan for your recording.
- Send your live link to the Idea → Live gallery: Add my site ↗
Help make Idea → Live better
How likely are you to recommend it to a friend?Your feedback contains your score, this text, your route, your live address and the dates you reached each step. Nothing else from your project.
Something isn't working
Open for the common problems with ready prompts. Still stuck: in Chat 2 (your build chat), attach a screenshot and describe in one sentence what you expected and what happened instead.
Found a mistake in this course, or a step that no longer matches what you see? Email Marta with the step number and a screenshot. It helps every learner after you.
Your data
Everything you typed and every screenshot is stored only in this browser on this device. It isn't synced or sent anywhere. Clearing your browser's site data, a private window or another browser starts empty. A backup file keeps everything, screenshots included: save one now and then, and restore it on any device. Got a new version of the course? Save a backup here, open the new file, and press Restore from backup there. You're on v1.5.8 beta.
Idea → Live is an independent product by Marta Jakovleva. It is not affiliated with, endorsed or sponsored by Anthropic or Higgsfield. Claude is a trademark of Anthropic.
Terms and privacy
Idea → Live is an independent product by Marta Jakovleva. Everything you type and every screenshot stays in this browser on this device. Nothing is sent to Marta unless you email it yourself.
The course gives step-by-step instructions for services run by other companies: Claude (Anthropic), Higgsfield, GitHub and Vercel. Each runs under its own terms and prices, which can change at any time, and their screens may differ from what is described here.
The course is a method, not a guarantee. How your site turns out depends on your answers, your choices and the tools on the day.
The bundled frontend-design skill is by Anthropic and is shared under the Apache License 2.0. The full licence text is included in its download.
Questions about the course or your data: laisaa.marta@gmail.com.