The complete Claude + Higgsfield workflow, from one creative brief to a website you can scroll through.
The plan
- 1Give Claude your business, visual direction, and a reference you love.
- 2Generate the scene with Higgsfield, then connect its motion to scrolling.
- 3Refine the website, check it on a phone, and prepare it for launch.
You can start this with a clothing brand, a restaurant, a product, or a completely fictional concept. Pick one clear subject and one thing you want the visitor to do. The rest of the page should support that.
What Creates the Cinematic Effect
Higgsfield generates an image and a short video of your scene. Claude builds a website that moves through the footage as you scroll, with real headings, buttons, and content layered around it. Scroll forward and the scene advances. Scroll backward and it reverses.
| Your brief | Starting still | Higgsfield video | Scroll website |
|---|---|---|---|
| Business + reference | Subject + composition | One camera move | Motion + real content |
This can look three-dimensional even though the visual is a rendered video or a sequence of frames. A real-time 3D website is different: the browser renders a scene with a camera, lights, and objects. You need that when people must rotate an object freely or interact with it from different angles.
Start with the version you actually need
| Your idea | Best starting point |
|---|---|
| A cinematic camera move controlled by scrolling | Higgsfield video turned into a scroll sequence |
| A subtle moving background | A short looping video, not a scroll sequence |
| A product people can rotate or configure | A real-time 3D scene, usually with a proper 3D model |
The master prompt is below. Fill in the brief, copy the whole prompt, and use the setup walkthrough afterward if anything is unfamiliar.
Maverick's tip
Build one excellent cinematic section first. You can add more once the first one looks good and works on a phone.
The Complete Master Prompt
Copy everything from START to END as one prompt. Replace the brackets. This is an original master prompt written for this workflow. It is not a copied prompt or a claim that the reference sites were built with these tools.
Master Prompt: Copy From Start to End
Set Up Claude Code
Make a place for the website
Create an empty folder with a simple name such as cinematic-website. This is where the website's files will live. Keep your logo, product photos, and written brief together so you can give Claude the actual material it needs.
Open the Claude desktop app, choose Code, select Local, and choose that project folder. Use the model picker near the prompt area to choose Fable. The desktop app can run and preview the website in the same session.
Choose the model and effort
The video uses Fable 5. Anthropic's current model page also lists Fable 5.1, so use the Fable version available to your account. Access depends on your plan and organization.
Set the separate effort control to Max for this initial build. Max is the deepest model reasoning level in Claude Code. Ultracode is a separate workflow setting, not another name for Max. If you're using the terminal version, /effort max sets the session's effort.
Maverick's tip
Max effort can consume more usage. You can reduce effort for small copy or color edits after the first build. The model setting won't replace a clear brief or a visual review.
Give it a useful starting point
| Bring this | Why it helps |
|---|---|
| Business name and one-sentence description | Keeps the page about something specific |
| Primary action and its destination | Gives the design a purpose |
| Your own logo and product photos | Helps preserve identity and product details |
| One reference URL and what you like about it | Gives Claude a concrete visual target |
| A generation budget | Keeps experimentation bounded |
For a first attempt, use a fictional concept if you don't have a business ready. Label it as a concept and keep invented business facts out of a real company's website.
Connect Higgsfield
MCP is the connection that lets Claude use another service's tools. Here, it lets Claude request images and videos from your Higgsfield account while it works on the website.
Desktop connector route
- In Claude, open Customize > Connectors. Some versions show Settings > Connectors.
- Add a custom connector named Higgsfield and use https://mcp.higgsfield.ai/mcp.
- Choose Connect, sign in to Higgsfield, and complete the authorization.
- Return to the local Code session. The + > Connectors menu lets you review available connections.
Prompt 2: Check Access Before Generating
Check which Higgsfield tools are available in this session without generating anything. Confirm whether you can search image and video models, use Seedance 2.5, retrieve completed assets, and save them into this project. Tell me what still needs connecting. Do not spend credits on this check.
Higgsfield requires an active paid subscription for this integration. Connected generations use credits, including when the website offers some unlimited generations. A prompt budget is an instruction to the agent, not a hard spending cap.
If you're using the standalone Claude Code terminal
Higgsfield also documents a CLI route. Ask Claude to follow Higgsfield's official connection instructions, install the official CLI and companion skills, then complete the browser sign-in yourself. You don't need both routes if one already works.
Maverick's tip
Seeing "connected" in a menu is a starting point. The no-spend check above tells you whether the current coding session can actually use the tools the master prompt needs.
Five Websites Worth Studying
These are visual references, not claimed Claude or Higgsfield builds. The first two are the examples supplied with this video. All five were opened and visually reviewed for this guide. Four use Vercel URLs. Study one specific design decision from each instead of combining every effect into one page.
1. DOORS: the portal entrance
An electric-blue doorway sits behind oversized white lettering. Scrolling draws you toward the glowing opening. It gives the page an immediate destination and a reason to move forward.
Model this: One strong focal point, a clear forward camera move, and type that belongs to the composition.
Adapt it: For a hotel, move through an entrance toward the view. For a studio, move through an abstract portal into selected work. Use your own scene and identity.
2. PeachWeb: a whole visual world
The opening uses a surreal fish, reflective forms, and a pastel landscape, with the offer and buttons placed over the scene. PeachWeb is itself a WebGL website builder, so treat this as inspiration rather than an extra tool required by this guide.
Model this: A coherent environment, a distinctive palette, and readable copy within an immersive scene.
Adapt it: Build one world around your subject. A skincare product could live in a soft mineral landscape. A restaurant might use warm light and a close-up tabletop scene.
Maverick's tip
In your reference field, say what you want to learn from the site. "The slow move through the doorway" is a better instruction than "make it like this."
3. Conoid: an abstract tech identity
A purple wire-like form provides depth behind bold, sparse typography. The scene carries a consistent mood while the page introduces the idea and its features. This demo is linked from DOORS.
Model this: A single abstract motif repeated across the experience, with enough restraint to keep the message readable.
Adapt it: For a software concept, use a controlled stream of particles or a sculptural object to represent the product. Avoid filling the page with unrelated futuristic effects.
4. Uma Jewellers: the product is the hero
A gold ring against a dark, warm background shares the first screen with large editorial type. The page then moves into collections and craftsmanship. Its creator describes the hero as a real-time WebGL ring.
Model this: Product lighting, negative space, and the transition from spectacle to useful shopping content.
Adapt it: Put your actual product in the scene and keep material, shape, and proportions accurate. A generated orbit can give a similar cinematic impression, but it won't become an interactive product configurator.
5. The Cosmos Within: scrolling as a journey
A dark starfield, luminous particles, and staged text create the feeling of moving through space. The creator documents a Three.js scene with scroll-driven camera waypoints.
Model this: A sequence with a beginning, middle, and destination, rather than a single effect repeated forever.
Adapt it: Use a journey to explain a process, explore a place, or introduce a fictional world. Keep each text section short enough to read without fighting the motion.
Turn a Reference Into Your Own Brief
A link gives Claude a target to inspect. It doesn't automatically provide the original source files, and it doesn't tell Claude which part you liked.
Give it the useful details
| Instead of this | Describe this |
|---|---|
| "Make it cinematic" | A slow camera push, deep shadows, one bright focal point |
| "Smooth motion" | Scroll forward and backward without jumps or blank frames |
| "Like the reference" | Its camera path and type scale, with a new subject and palette |
| "Make it premium" | Restrained colors, careful spacing, accurate imagery, strong typography |
| "Make it 3D" | A rendered scene on a fixed path, or a freely interactive 3D object |
Prompt 3: Reference Breakdown
Study [reference URL] using the browser tools available to you. Explain its hero composition, camera movement, text timing, section transitions, and mobile treatment. Separate what you observed from what you're inferring about the implementation. Suggest how to apply those principles to [my business] with original assets and copy. If you cannot inspect the motion, say so and tell me which screenshots or screen recording would help.
What "pull the code" really means
Claude may be able to inspect files a website sends to the browser. Those files are often bundled or minified, and they are not the same as the author's original project. A URL also doesn't expose server-side code or private data.
Use the reference to understand a technique. If you want reusable code, provide your own project or an explicitly licensed template and keep the required attribution. For this workflow, a clean original implementation is usually easier to maintain than reconstructing somebody else's bundle.
Maverick's tip
Pick one primary reference. Use a second only for a specific detail, such as typography or a mobile layout.
Plan the Scene Before the Video
The biggest improvement often happens before generation. Decide what the camera is doing and where the text will sit. One continuous move is easier to connect to scrolling than a montage of unrelated shots.
A simple three-beat storyboard
| Beat | Visual | Website content |
|---|---|---|
| Establish | Show the complete subject with room around it | Brand, short promise, main action |
| Explore | Move closer, orbit slightly, or reveal a detail | One useful benefit or story point |
| Resolve | End on a stable, deliberate composition | Product detail or invitation to continue |
- Establish. Give the subject room.
- Explore. Move closer to a detail.
- Resolve. Land on the main action.
Choose one kind of movement
Dolly: The camera travels toward or away from the subject. Useful for entrances, spaces, and product reveals.
Orbit: The camera moves around the subject. Useful for a shoe, bottle, watch, or sculptural object. A shallow arc is often easier to keep consistent than a full revolution.
Reveal: Something moves aside or the camera passes an obstruction. Useful when the final view is the payoff.
Write the shot in one sentence
"Move slowly toward a charcoal running shoe on a black stone platform, ending close enough to see the knit texture, with empty space on the left for the headline."
That sentence gives you a subject, setting, move, ending, and place for the copy. Add lighting and materials next. Don't ask for five camera moves in a single short clip.
Create the Starting Image
A strong still gives the video a clear visual target. If you're showing a real product, attach clean product photos and ask Claude to preserve its identity. Check the output before using it as the basis for motion.
Prompt 4: Starting Image
Using the connected Higgsfield image tools, create a cinematic starting frame for [business or concept]. Main subject: [subject]. Setting: [environment]. Materials and lighting: [details]. Palette: [colors]. Composition: [subject position] with clear negative space at [text area]. Use the attached product reference accurately if supplied. Keep logos and website text out of the image. Plan a crop that also keeps the subject visible on a phone. First show the chosen model, supported settings, and credit estimate, then follow my approved budget.
Check the still at website size
Look at the image wide, then imagine a narrow phone crop through its center. Is the subject still recognizable? Is there enough space for the title? Does the lighting give the background depth without swallowing the product?
| Check | Reject or revise when |
|---|---|
| Identity | The product shape, label, or material has changed |
| Composition | The subject collides with the planned headline |
| Crop | The phone version loses the important part |
| Detail | Edges, reflections, hands, or repeated objects look wrong |
| Copy space | Every area is too busy to hold readable text |
Maverick's tip
Use a still-image model for stills. Seedance 2.5 is the video part of this workflow. You don't need to make every supporting website image into a video.
Generate the Cinematic Clip
Ask Claude to animate the starting image through Higgsfield using Seedance 2.5, where it is available in the connected tools. Higgsfield documents both reference-based video generation and a separate editing model. Supported settings can differ between the website and the connected tool, so have Claude check them first.
Prompt 5: Scroll-Sequence Video
Use this approved image as the visual reference for one continuous cinematic shot with Seedance 2.5 through Higgsfield, if supported here. The camera [describe one controlled move] from [starting view] to [ending view]. Preserve the subject's identity, geometry, materials, and lighting throughout. Keep [area] visually calm for website text. No cuts, transitions, sudden acceleration, handheld shake, morphing, new objects, logos, or baked-in words. Favor clean, steady motion that still looks good when paused or scrubbed backward. Aim for a short 5-8 second shot using supported settings. No audio is needed for the website. Stay within my approved generation budget.
Watch it more than one way
Play the clip normally, then pause at several points. Scrub backward. Check whether the product changes shape, the room shifts, the camera jumps, or the subject exits the mobile crop. The website will expose intermediate frames that a normal video viewer might barely notice.
Keep a record of the asset
Save the approved original, generation prompt, model/settings, and job reference. Keep a separate optimized web version so you can revise compression without losing the original quality. An asset URL returned by a generation tool may not be the durable public URL you want on a finished website.
Maverick's tip
Five to eight seconds is a starting creative brief, not a required model limit or guaranteed best length. The visitor controls how quickly they move through the finished sequence.
Make Scrolling Control the Scene
This is the step that turns a nice background into the effect from the video. A looping background plays on its own. A scroll-controlled sequence follows the visitor's position through a specific section.
How the connection works
Claude calculates how far the visitor has moved through the scene, from 0% to 100%. It maps that progress to a timestamp or frame. GSAP ScrollTrigger supports scroll-linked animation and pinned sections. Browser video elements expose a playback position through currentTime.
| 0% | 50% | 100% |
|---|---|---|
| First frame | Middle frame | Last frame |
Scroll forward to advance. Scroll backward to reverse.
Two implementation choices
| Method | What to ask Claude to watch |
|---|---|
| Seek through a video | Encoding and device behavior affect how evenly it jumps between times. Test it rather than assuming playback quality means good seeking. |
| Draw a frame sequence to canvas | Frames give direct control, but downloads, decoding, and memory can grow quickly. Use bounded loading and a lighter mobile version. |
Prompt 6: Motion Implementation
Turn the approved hero media into a reversible scroll sequence. Keep native page scrolling and one bounded sticky scene. Use the same progress value for visual position and text cues. Show a poster immediately and preserve the last available frame during loading. Test video seeking first, then explain whether an optimized frame sequence would improve this specific asset. Check fast scroll, reverse scroll, resize, and reload midway. Keep readable HTML content outside the canvas and provide a static reduced-motion version.
Maverick's tip
Don't ask Claude to add smoother scrolling until the basic sequence works. More smoothing can make the scene feel delayed instead of polished.
When You Actually Need Real 3D
Use the video approach when the visitor follows a fixed camera path. Choose real-time 3D when the experience needs new views or object behavior that wasn't already rendered into the clip.
| Interaction | Video or real-time 3D? |
|---|---|
| Move through a room on one planned path | Video can work |
| Scrub forward and backward through a product reveal | Video or frame sequence can work |
| Rotate a product freely with a pointer | Real-time 3D |
| Choose materials and inspect them from arbitrary angles | Real-time 3D |
| Walk around an environment freely | Real-time 3D |
Three.js is a JavaScript library for rendering 3D scenes in the browser. It provides the building blocks, such as scenes, cameras, geometry, materials, and lights. React Three Fiber is an option when you want to work with Three.js in a React project.
Prompt 7: If Your Concept Needs That Route
This website needs [free rotation / material choices / another real interaction]. Explain which parts require real-time 3D and build those with Three.js or React Three Fiber if appropriate for the project. Use [my supplied 3D model] or clearly identify any missing model. Higgsfield video can remain supporting media, but don't describe it as an interactive 3D model. Keep a static fallback and test touch controls, keyboard access, loading, and performance.
A generated video does not automatically give you a usable 3D model. If you don't already have the model, decide whether a simple original shape is enough or whether the product needs proper modeling. This changes the scope of the build.
Maverick's tip
A hybrid is fine. Use an actual 3D product viewer where it helps, then use lighter stills and normal sections elsewhere.
Make It Work on a Phone
The desktop reveal is only half the job. On a phone, the camera crop is narrower, the screen has less room for copy, and the device has less room for expensive visual work.
Make a deliberate mobile version
- Keep the subject inside a safe crop throughout the shot, or use a separate portrait asset.
- Shorten the sticky scene if it makes visitors scroll too far before reaching useful content.
- Move the headline or supporting copy into a solid section when an overlay becomes hard to read.
- Use appropriately sized assets and avoid holding an entire large frame sequence in memory.
- Keep the main action reachable even if motion never loads.
Prompt 8: Mobile and Accessibility Repair
Review this site on a narrow phone viewport and, where available, a real mobile browser. Fix subject cropping, horizontal overflow, tiny text, inaccessible menus, blocked buttons, and excessive scroll distance. Measure the largest media downloads and reduce waste. When prefers-reduced-motion is enabled, show a deliberate static layout with the same content and working actions. Check keyboard focus and a failed-media state. Report what you actually tested and what still needs a device check.
Reduced-motion preferences let a visitor ask for less animation. The browser exposes that preference so the website can provide a calmer version.
A useful performance check
Ask Claude for actual download sizes and observed problems before asking for a perfect score. A page can look smooth on a powerful laptop and still struggle on a phone. Test an initial visit, a slow connection, and a visitor who immediately scrolls to the bottom.
Maverick's tip
The static version should still look designed. Use the strongest frame, clear text, and a working button instead of an empty rectangle.
Example Build 1: A Clothing Brand
Fictional concept: STONE / FORM, a small technical outerwear label. The goal is to explore the collection. Use your real product and store details if adapting it for an actual brand.
Fill the master prompt with this direction
| Brief field | Example |
|---|---|
| Visual subject | One charcoal jacket suspended in a dark studio |
| Mood | Tactile, restrained, precise |
| Camera | Slow shallow orbit, ending close to a seam detail |
| Palette | Charcoal, off-white, one muted accent |
| Main action | Explore the collection |
| Reference lesson | Uma's product focus and Conoid's restraint |
Suggested page flow
Start with the full silhouette and a short brand line. Move toward the material as the visitor scrolls. End the scene before introducing a clean product grid, sizing information, delivery details, and a direct route to the real store.
Prompt 9: Add This to Your Brief
Build this as a tactile outerwear launch. Keep the jacket the clear subject, with subtle motion and accurate fabric detail from my reference images. Use one hero sequence, then let the product information breathe. Put garment names, prices, and labels in HTML. Connect only the store links I provide. A cinematic launch page is the goal, not a pretend checkout.
Maverick's tip
For a real garment, reject generated changes to pockets, fasteners, logos, or fit. Use exact product photography where accuracy matters more than motion.
Example Build 2: A Restaurant
Fictional concept: EMBER HOUSE, an intimate wood-fired restaurant. The main action is to reserve a table. The page needs to communicate the food, atmosphere, location, and how to book.
Fill the master prompt with this direction
| Brief field | Example |
|---|---|
| Visual subject | A plated dish on a warm stone table |
| Mood | Warm, intimate, generous |
| Camera | Gentle push toward the dish with subtle steam |
| Palette | Deep brown, warm cream, ember red |
| Main action | Reserve a table |
| Reference lesson | DOORS' sense of arrival, applied with restraint |
Suggested page flow
Open on a scene with room for the restaurant name and reservation button. Let the camera move closer as a short food philosophy appears. Then release the visitor into the menu, location, hours, dietary information, and booking details.
Prompt 10: Add This to Your Brief
Make the restaurant feel warm and inviting. Use one continuous tabletop shot with a gentle camera push, stable crockery, and restrained steam. Keep the actual menu, hours, address, and booking link easy to find without watching the full sequence. Use supplied food photography for real dishes and label concept visuals appropriately. Don't invent awards, reviews, or a working reservation system.
Maverick's tip
Atmosphere supports the booking. It shouldn't make someone hunt for the address or wait through an animation to see the menu.
Example Build 3: A Business That Doesn't Exist Yet
Fictional concept: ORBIT, a speculative software product for planning ambitious projects. The goal is to explain the concept and invite interest. There are no real customers or product claims to imply.
Fill the master prompt with this direction
| Brief field | Example |
|---|---|
| Visual subject | A luminous sculptural ring in a dark abstract space |
| Mood | Calm, futuristic, focused |
| Camera | Slow passage toward the ring, ending at its center |
| Palette | Midnight blue, soft violet, white |
| Main action | Explore the concept or join a real waitlist |
| Reference lesson | Conoid's motif and Cosmos' staged journey |
Suggested page flow
Use the opening to introduce the idea. Let three short scenes explain the intended problem, approach, and outcome. Then show a clearly labeled concept interface and a concise FAQ. A waitlist needs an actual configured destination before you call it live.
Prompt 11: Add This to Your Brief
Build an original concept site for ORBIT. Use one luminous abstract object as the visual thread through the experience. Make three concise story beats, then show a clearly labeled concept interface. Keep all benefits framed as the proposed product vision. No invented users, funding, partners, testimonials, or usage numbers. If the waitlist isn't connected, show that clearly in the local preview.
Maverick's tip
A fictional business is a good place to practice bold art direction. Keep the concept label visible if you share it publicly.
The Polish Pass That Makes the Difference
The first generation gives you material to work with. The next pass should be specific. Don't ask Claude to redesign the whole thing every time one transition feels wrong.
Review it in this order
| Pass | Look for |
|---|---|
| Composition | A clear subject, readable first screen, intentional spacing |
| Motion | Clean start and end, reversibility, no awkward pauses or jumps |
| Content | Real facts, useful sections, concise copy, a clear action |
| Function | Working navigation, honest form states, correct links |
| Delivery | Sensible loading, mobile layout, static fallback, complete files |
Prompt 12: Focused Refinement
Review the actual preview against our brief and reference notes. Identify the three most visible weaknesses, then fix them without replacing the successful parts. Focus on [specific issue]. Use screenshots or browser observations to explain the before-and-after difference. Keep the approved asset unless it is the source of the problem. Run the relevant checks again and tell me what remains unfinished.
Better feedback examples
"The headline is unreadable halfway through the move. Keep it on a solid panel during that section."
"The camera takes too long to reach the product. Shorten the scroll distance and reveal the details sooner."
"The product looks good, but the next three sections are identical card grids. Give the specifications, story, and FAQ layouts that fit their content."
Maverick's tip
Change one major variable at a time. It is much easier to judge the result when the asset, layout, and motion aren't all being replaced together.
From Local Preview to a Live Website
A local preview runs on your computer. Deployment puts the built website on a host so other people can visit it. Vercel supports preview and production deployments from a connected Git repository or its CLI, and each deployment has its own URL.
Prompt 13: Ask for the Launch Package First
Prepare this project for deployment to Vercel. Verify the production build, include all required assets, and document exact setup and build commands. Identify missing integrations, placeholder content, environment variables, media-hosting needs, and any hosting-plan limits I should check. Keep generation credentials out of browser code and the repository. Show me the proposed project and destination, but don't upload or publish until I approve it.
The basic launch sequence
- Review the local site and approve its content and assets.
- Choose the Vercel account and project. Confirm the site's intended audience and access settings.
- Deploy using the supported project workflow. If you use the CLI, vercel deploy creates a deployment and vercel deploy --prod targets production.
- Open the resulting URL and check it again. Local success is not proof the hosted assets and links work.
- Connect a custom domain if you want one, then verify that domain too.
Before you share the URL
Check the phone layout, every primary button, media loading, page title, social preview, and contact details. Submit a test form only to a destination you control and confirm what actually arrived. If payments or reservations are involved, use the provider's test workflow before going live.
Maverick's tip
Host the finished media as website assets. Keep AI generation in the creation process, so visitors don't need a Higgsfield account or trigger a new generation to load your page.
Mistakes and Fixes
| What went wrong | What to ask Claude to fix |
|---|---|
| The background plays independently | Tie scene position to section scroll progress rather than autoplay. |
| Motion jumps when scrolling backward | Check seek behavior, encoding, frame readiness, and competing animation loops. |
| A black or blank scene appears | Render a poster immediately and preserve a valid frame while loading. |
| The phone crop cuts off the product | Reframe the scene or use a dedicated mobile asset. |
| The website waits behind a loader | Make text and actions available while media loads progressively. |
| Scrolling feels slow or trapped | Reduce smoothing, shorten the pinned section, and restore normal flow. |
| The product changes shape | Fix the asset or use accurate photography instead of hiding the problem with code. |
| Higgsfield works elsewhere but not here | Run the connection check in this exact Code session. |
| Seedance 2.5 isn't listed | Check the connected catalog and propose an available model without pretending it is the same one. |
| Every button leads nowhere | Connect real destinations or mark features as unfinished. |
| The page looks like a copied demo | Keep the technique and replace the composition, content, and assets with an original direction. |
| The preview works but the live site fails | Check production asset paths, missing files, build settings, and browser errors. |
One prompt is the starting brief
The master prompt is designed to carry the whole project, including generation, coding, review, and handoff. You may still need to sign in, approve a generation batch, provide missing business details, or choose between creative options. Judge the working website, not whether the entire process fit into one uninterrupted response.
Quick Reference
The whole build, in order
| Stage | What to do |
|---|---|
| Brief | Name the audience, subject, action, reference, and budget. |
| Claude | Open Code, choose a local folder, select Fable and Max effort. |
| Higgsfield | Connect the account and run the no-spend access check. |
| Master prompt | Paste the complete START-to-END prompt with your brief. |
| Starting still | Approve identity, composition, lighting, and phone crop. |
| Video | Generate one controlled continuous shot with supported settings. |
| Scroll | Map progress to video time or frame position in both directions. |
| Website | Keep headings, buttons, and useful content in real HTML. |
| Quality | Check phone layout, reverse scroll, loading, reduced motion, and links. |
| Launch | Review the production build and approve the intended deployment. |
Three combinations to try
Clothing: Product still + shallow orbit + clean collection section.
Restaurant: Warm tabletop scene + gentle push + easy reservations.
Concept business: Abstract object + staged journey + honest concept copy.
Do this today. Choose one business idea and one reference. Fill in the master prompt's brief, connect Higgsfield, and build a local prototype with one hero sequence. Get that sequence working forward, backward, and on a phone before adding more effects.
Make the scene worth watching. Make the website worth using.
Published · Checked