Build a Cinematic Scroll Website with AI

Download and install Claude Desktop

Download Claude Desktop

https://claude.com/download

Create an empty project folder

Open the folder in Claude Desktop

Claude Desktop Code Local Select the project folder Open Trust Workspace

Connect Higgsfield to Claude

This lets Claude create the images and video for your website.

Open the Higgsfield MCP page

https://higgsfield.ai/mcp

Copy the connector URL.

Claude Desktop Customize Connectors Add custom connector

Name it “Higgsfield,” paste the URL, then connect and sign in.

Customize your website

Pick a few options. The most important one is your Signature Scroll Concept — what happens as the visitor scrolls. Leave it on Let Claude Recommend to get three ideas to choose from.

Build the Cinematic Scroll Website

Choose a few options, then copy one prompt. Claude suggests concepts, shows a short plan, creates the visuals and builds your website.

Build a premium cinematic scroll website in this project folder for {{PROJECT_NAME}}. Use the connected Higgsfield MCP for all image and video generation. Do not use Higgsfield's website builder or hosting — build the website here, in this folder. Do not ask me to install creative tools. If you need an ordinary local tool while building, set it up yourself, and only when it is genuinely necessary. PROJECT - Niche: {{NICHE}} - Main website goal: {{PRIMARY_GOAL}} - Main call to action: {{MAIN_CTA}} - Additional instructions: {{ADDITIONAL_INSTRUCTIONS}} CREATIVE DIRECTION - Visual direction: {{VISUAL_DIRECTION}} - Inspiration: {{INSPIRATION}} VISUAL SOURCE {{VISUAL_SOURCE}} MOBILE {{MOBILE_EXPERIENCE}} GROUND RULES - Treat any inspiration I give you — above, or images in an "inspiration" folder in this project — as direction only: mood, pacing, composition and feel. Never copy its text, images, branding, logos, proprietary assets or overall identity. - If this is a real business, property, product, place or service, keep its real identity exactly as it appears in my material. Never invent features, specifications, rooms, facilities, business claims or product capabilities. My own media is the source of truth. - Keep everything focused on this niche and on moving visitors toward the main goal. WORK IN THIS ORDER 1. SIGNATURE SCROLL CONCEPT — what happens as the visitor scrolls: one memorable cinematic idea, not a generic fade, zoom or parallax effect. {{SCROLL_CONCEPT}} 2. PLAN — once the concept is settled, and before any paid Higgsfield generation Show me a short, plain-language plan: - The Signature Scroll Concept - The visual direction - The main cinematic visual and what happens in it as I scroll - The website sections around it - The Higgsfield images and video you will create, and how you will use my own media, if any - The expected Higgsfield usage, and my current balance, if you can check them Keep it short and non-technical. Then stop and wait for my approval. 3. MAIN CINEMATIC VISUAL After I approve, use Higgsfield to create ONE strong main cinematic sequence for the scroll experience — not a series of separate videos — plus still images only where they clearly improve the website. Save everything in this project. Then show me the main visual and ask me: Use It or Change It? If I ask for a change, regenerate only what needs changing and keep everything I already approved. Do not build the rest of the website until I choose Use It. 4. BUILD THE WEBSITE Then build the complete website around the approved visual: - A strong homepage structure for this niche — a real premium website, not just a video demo - The cinematic visual as the centrepiece, moving smoothly with scroll progress - Useful sections with finished, specific copy — no placeholder text - Working navigation and buttons, ending on the main call to action - Fully responsive, with a great experience on phones - Fast loading Choose the implementation yourself and handle the technical details without asking me technical questions. Then run the website locally and give me the preview address.

Leave these as they are if you are not sure.

Project or Brand Name

e.g. Ember Coffee

Niche

Choose a niche

Primary Website Goal

Choose a goal

Main Visual Source

Choose an option

Visual Direction

Choose an option

Signature Scroll Concept

Choose an option

Inspiration (Optional)

A website link or a short note

Main Call to Action

Choose an option

Mobile Experience

Choose an option

Additional Instructions

Optional — anything Claude must include or avoid

Add your files (optional)

Only if you chose your own media, or have images you like for inspiration.

Project folder reference-assets

Your real photos, videos, logos and brand documents. Claude treats them as the truth about your business.

Project folder inspiration

Screenshots or images you like, for style only. Claude never copies them.

Send the prompt to Claude

Paste it into Claude in your project folder and send it.

Choose a concept and approve the plan

Pick one of Claude's concepts (or keep your own), then read the short plan and approve it. Nothing paid is generated before you approve.

Review the cinematic visual

Claude creates the main visual with Higgsfield and shows it to you. Reply Use It to continue, or Change It and say what should be different.

Let Claude build the website

Claude builds the full website around the approved visual. This can take a while — you do not need to do anything.

Open the local preview

Open the preview address Claude gives you when the website is ready.

Check the scroll effect

Scroll slowly from top to bottom. The visual should look sharp and move smoothly, with no flashes, jumps, awkward cuts or strange changes.

Check the pacing and content

Make sure the effect is not too fast or too slow, the text is easy to read, the content fits your business, and every button and the final call to action work.

Check desktop and mobile

View the website full-width on a computer, then on a phone. The visual, text and buttons should fit and stay easy to use on both.

Request corrections

Request Targeted Corrections

Click Customize Prompt, describe what to fix, then copy the prompt.

Apply only these corrections: {{CORRECTIONS}} Keep everything else exactly as I approved it. Do not regenerate approved Higgsfield images or video unless a correction genuinely requires it. If a correction needs a new paid Higgsfield generation, first tell me what needs to be regenerated and wait for my approval. Then run the website locally again and tell me exactly what changed.

What to Fix

e.g. Slow down the scroll effect and make the headline bigger on phones

Get Hostinger hosting

Your website is ready. Now it needs a home online.

Get Hostinger Hosting

Recommended plan: Unlimited (formerly Business)

USED IN TUTORIAL

Already have Hostinger hosting? Continue below.

Connect Hostinger to Claude

Already connected Hostinger to Claude? Skip to the next task.

Stay in Claude Desktop, in the Code session for this project. Click + next to the message box, then open the plugins:

+ Plugins Add plugin

Find Hostinger in the plugin list and install it. The first time Claude uses Hostinger, sign in to your Hostinger account in the browser window that opens and allow access.

No API token or settings file needed — you only sign in.

Deploy the website

Send this prompt to Claude in the same Code session. Claude asks which Hostinger website to use, builds your website and puts it live.

Deploy the Website to Hostinger

Publish your approved website to Hostinger and get the live URL.

Publish this approved cinematic website to my Hostinger account with the Hostinger tools. BEFORE PUBLISHING - Use the Hostinger tools from the Hostinger plugin. If they are not available, or I am not signed in to Hostinger, stop and tell me how to connect Hostinger. Never ask for my password, and never write a token or key into any file. - Inspect this project first: how it builds, and which folder holds the finished website. - If .hostinger/site.json exists in this project, publish to the website it names. - Otherwise, list my Hostinger websites and ask me which one to use, or offer to set up a new website on a free temporary Hostinger domain. Never guess. Tell me that publishing replaces everything on that website, and only continue once I have confirmed it. BUILD AND PACKAGE - Keep the website and all of its visuals exactly as I approved them. Do not regenerate any Higgsfield images or video, and do not redesign or rewrite anything. - Run the production build. If it fails, fix only the build error — never publish a website that does not build. - Check that the finished website includes every image, video and other media file it uses, and that none of them points to a file elsewhere on my computer or to a temporary link. - Package the CONTENTS of the finished website folder as one archive, with index.html at the top level — never the project source, node_modules, or any .env file. PUBLISH AND CHECK - This website runs in the browser, so deploy the archive to the confirmed website as a static website. If the project genuinely needs a server to run, stop and tell me before publishing. - Open the live address and check that it shows this cinematic website — its real content, main visual and scroll effect — not a placeholder page. - If the deployment fails or the live website is wrong, check the deployment details with the Hostinger tools, fix the cause in this project, build again, and ask me before publishing again. - Save the website's domain in .hostinger/site.json, so later updates go to the same website. Save only the domain — never a token or a key. When it is live, give me the live address and tell me about any change you had to make for deployment.

Publishing replaces everything on the Hostinger website you choose. Use a new website, or one you want to replace.

Review the live website

Open the live URL and check the cinematic scroll effect, the images and video, the content, every button and the main call to action — on desktop and on mobile.

Connect your domain

Optional. Already have a domain? Claude can connect it to the website for you — add it here and send the prompt.

Connect My Domain

Click Customize Prompt, add your domain, then copy the prompt.

Connect my domain {{DOMAIN}} to the website you just published, using the Hostinger tools. - The website is the one saved in .hostinger/site.json. If that file is missing, or you are not sure which domain I mean, ask me — never guess which website or domain to change. - First check that the domain is in my Hostinger account. If it is not, or the connection needs something only I can do, tell me exactly what to do and wait. - Change only what is needed to point the domain at this website. Leave the website itself unchanged, and do not touch any other domain settings, such as email records. - Only give me manual DNS steps if the Hostinger tools genuinely cannot make the change. - If the website's main domain changes, update .hostinger/site.json so later updates still go to this website. When finished, tell me whether the domain is connected, which address to open, and anything I still need to do, such as waiting for the change to take effect everywhere.

Your Domain

e.g. mybrand.com

Publish future updates

Describe your change and send this prompt. Claude makes the change and shows you a local preview first. When it looks right, reply Publish — only then does Claude publish it to your Hostinger website.

Publish an Update

Click Customize Prompt, describe your change, then copy the prompt.

Update my website in three stages. Stop after stage 2 and wait for my approval. 1. CHANGE Make only this change: {{CHANGE}} Keep everything else exactly as it is, especially the approved cinematic visuals. Do not regenerate any Higgsfield images or video unless this change genuinely requires it. If it needs a new paid Higgsfield generation, tell me what you would regenerate and wait for my approval first. 2. LOCAL REVIEW - Run the production build and fix any error the change caused. - Run the website locally, give me the preview address, and tell me in one or two lines what you changed. - Then stop. Do not publish anything until I reply Publish. If I ask for adjustments instead, make them and show me the preview again. 3. APPROVED PUBLISH — only after I reply Publish - Publish to the same Hostinger website as before: the domain saved in .hostinger/site.json. If it is missing, ask me which website to use — never guess. - Publish exactly what I approved. Do not make any other change first. - Run the production build again. If it fails, stop and tell me why instead of publishing — never fix it on the way. - Check that the finished website includes every image, video and other media file it uses, then package the CONTENTS of the finished website folder as one archive, with index.html at the top level — never the project source, node_modules, or any .env file. - Deploy it to that website as a static website with the Hostinger tools. - Open the live address, check that it shows the approved change, and give me the live URL.

Your Change

e.g. Change the headline to Freshly Roasted Every Morning