You can spot an AI-built site from across the room now. Centered hero, a headline in a heavy sans, two rounded buttons, a soft gradient blob glowing behind everything, three feature cards with icons. It's not ugly. It's worse than ugly — it's familiar, in the way that tells a visitor "nobody made a decision here."
Here's what makes this genuinely strange: the same AI coder that produces that default will happily build you a scroll-driven 3D scene, a hero that plays like a film, a page that feels like it cost five figures. I know because building those is a large part of what I do — this site's own front page is a scroll-scrubbed frame sequence an AI agent and I built together. The model was never the bottleneck.
The bottleneck is vocabulary. And there's now a small market selling exactly that — prompt libraries for cinematic UI. This is an analysis of that market through its clearest example: VividSites, the library until recently known as uiprompts.
The generic-site problem is not a model problem
When people say "AI sites all look the same," they usually blame the model, as if it can only produce one design. That diagnosis doesn't survive contact with the tools. Ask an agent for "a landing page for my SaaS" and you get the default I described, because the prompt contained zero design decisions and the model filled the vacuum with the statistical average of every landing page it's seen.
Now describe the same page the way a motion designer would — a full-bleed WebGL scene that parallaxes at a third of scroll speed, a serif display face at a size that feels slightly reckless, a camera that eases in over 1.2 seconds, light that behaves like it's coming from somewhere — and the same model, the same tool, produces something that looks like money.
The model fills whatever design vacuum you leave with the average of everything it has seen. "Generic" isn't the AI's style. It's the absence of yours.
The catch is that writing that second prompt requires knowing the words. "Scroll-scrub," "specular highlight," "easing curve," "depth of field" — this is a vocabulary most developers never needed until the moment the coding stopped being the hard part. Vibe coding moved the bottleneck from can you implement it to can you describe it, and an entire skill gap opened overnight on the describing side.
Enter the prompt library
Which brings us to the product category. A cinematic prompt library sells you pre-written descriptions: you browse rendered previews of finished sections — heroes, landing pages, 3D scenes, backgrounds — pick one, copy its prompt, and paste it into whatever AI coder you already use. You're not buying code, exactly. You're buying someone else's articulation of a design, in a form your agent can execute.
VividSites is the cleanest specimen of the category I've seen. First, a housekeeping note that matters if you've heard of it before: it launched as uiprompts.app, and that domain now permanently redirects to vividsites.app — same product, rebranded. I verified the redirect myself while writing this, because a category this young has a lot of lookalike names floating around.
What the library holds, per its own catalog at the time of writing: 166 templates, organized into hero sections, landing pages, 3D sections, backgrounds, and full templates, targeting stacks from plain HTML/CSS and React/Tailwind up to Three.js and WebGL2. Each premium prompt ships with the source video of the finished result — so you see exactly what the prompt produces before you spend anything on it. Around twenty of the templates are free, which is the detail I'd act on first, and the paid tier is a single "unlock all" covering every premium prompt and future additions. The exact price sits behind the checkout rather than on a public pricing page, so I won't quote a number I'd be guessing at — check it yourself before deciding anything.
What you're actually paying for (and what you aren't)
It's worth being precise about the value here, because "paying for prompts" sounds absurd to half the developers reading this. You can write prompts. Prompts are just words. Why would words cost money?
Three reasons the market exists anyway:
- The words are the distilled part. A prompt that reliably produces a specific cinematic hero encodes dozens of design decisions — typography scale, motion timing, lighting, composition — that took someone iterations to converge on. You're paying to skip the convergence, not for the ASCII.
- The preview collapses the risk. The classic failure of buying themes is discovering the gap between screenshot and reality. A prompt sold with the source video of its own output inverts that: you've seen the destination before you start.
- It's a design education you absorb by accident. This is the underrated part. Read ten well-written cinematic prompts and you start noticing how they specify things — what gets a number, what gets an adjective, what gets named precisely. That vocabulary stays with you after the prompts run out.
And what you're not paying for, stated just as plainly: exclusivity and fit. A popular template library means other sites will share your design's DNA — you're escaping the AI-default sameness by joining a smaller, better-dressed sameness. And a prompt written against a generic project won't know your brand, your content structure, or your constraints; there is always an adaptation pass, and on the 3D-heavy end that pass assumes you can debug what the agent produces when WebGL misbehaves.
Where this fits against the alternatives
| Approach | You get | The honest catch |
|---|---|---|
| Default AI output | A working site in minutes, free | Looks like everyone else's working site |
| Prompt library | A distinctive design language, executable by your own agent | Adaptation pass required; shared DNA with other buyers |
| Learning the vocabulary | Permanent skill, infinite variations, true distinctiveness | The slowest option; taste takes longer than syntax |
| Hiring a designer | Actual originality and accountability | The price is the point — it's what the other three exist to avoid |
My actual position, as someone on the "learned the vocabulary" path: the library and the learning aren't rivals. The prompts are worked examples — the fastest way I know to learn how motion and light get specified is to read specifications that demonstrably work. Buy or borrow the articulation, then steal the grammar.
Who should act on this
Start with the free tier if you're curious at all — twenty-ish real templates is an unusually honest trial for this category, and one paste into your own agent will tell you more than this article can. The unlock makes sense for people shipping client sites or multiple launches, where "distinctive in an afternoon" has direct monetary value and the cost amortizes across projects. Skip it if you ship one internal tool a year, if your product's value is unrelated to visual drama — a dashboard doesn't need a film-grade hero — or if you'd rather spend the money on a month of slow evenings learning to write the prompts yourself, which remains the only option on this list nobody can rebrand out from under you.
Sources
- vividsites.app — template count (166), categories, stacks, free templates, and the unlock-all model, as shown in the public library on August 20, 2026
- uiprompts.app → vividsites.app permanent redirect (HTTP 308) — verified directly, August 20, 2026
- The scroll-scrubbed hero referenced above is this site's own front page; its build log is here