AI Prompt Generator for Cinematic Websites
Fill in the blanks and copy — 7 staged AI prompts for a cinematic, animated website: creative direction, experience architecture, the hero section, the motion system, a step-by-step build plan, a polish audit, and a pre-launch audit.
Fill in the blanks below — the prompt updates live. These work with any AI chat tool (Claude, ChatGPT, Gemini, etc.); nothing here is tied to one specific model.
How it works
These prompts run in order. Start with creative direction to fix the concept, then map the experience section by section, then specify the hero and the motion system — the two parts that are hardest to get right and easiest to overdo. The build plan (#5) turns all of that into a sequence of smaller prompts you feed to a coding assistant one at a time.
Keep the constraints the prompts ask for. Every one of them requests a reduced-motion fallback and a performance check, because the difference between a cinematic site and a slow, janky one is usually whether those were treated as requirements or afterthoughts.
The two audit prompts (#6 and #7) work on any existing site, not just one built this way. Run the polish audit when something feels generic but you cannot say why, and the launch audit before you point a domain at it.
FAQ
Can AI really build a $20,000 agency website for free?
That framing is marketing. AI chat tools can generate animated front-end code, but a polished result comes from several rounds of iteration and review, not one prompt. Free plans of Claude, ChatGPT, and similar tools are usage-limited, so sustained building usually needs a paid plan or an API budget. You also still handle what an agency handles: hosting and deployment, a real domain, licensed images and fonts, performance budgets, and testing on real devices.
Why is the work split into seven prompts instead of one?
Because asking for a whole cinematic site in one prompt produces a shallow result. Splitting it lets each stage go deep — the creative direction sets the concept, the experience map sequences the page, the hero and motion prompts specify the hard parts, and the build plan turns it into incremental steps. Each stage's output feeds the next.
Do heavy scroll animations hurt site performance?
They can. Parallax, pinned sections, and large scroll-driven effects add load time, can cause layout jank on low-end phones, and can trigger motion sickness. Every prompt here asks for a reduced-motion fallback and a performance budget for that reason — keep those requirements in when you run them, and test on a mid-range phone, not just your laptop.
Which AI tool should I use to actually build the site?
Any capable coding assistant works — Claude (including Claude Code), ChatGPT, or an IDE-integrated tool. The build-plan prompt (#5) is written to produce a sequence of smaller prompts that each inspect the existing code, make one change, and test it, which is the pattern that works best regardless of tool.
I only need to improve an existing site, not build a new one. Which prompts apply?
Use the Polish Audit (#6) to find what reads as generic or unfinished, ranked by visual impact, and the Launch Audit (#7) for a full pre-launch pass across UX, accessibility, SEO, and speed. You can also run the Motion System prompt (#4) on its own if the site needs animation added carefully.