You've been here before. You open v0, Lovable, or Bolt.new. You type "build me a pricing page," hit enter, and get back something that looks like every other 2023 SaaS pricing page. So you try again. "Make it more modern." Still off. "Use shadcn/ui, dark mode, with a billing toggle." Closer. Three more re-prompts later you've spent 25 minutes getting something you could have built by hand in 20.
The problem isn't the AI builder. It's the prompt. Vague prompts produce vague output. Generic prompts produce generic output. The fastest engineers I know don't re-prompt — they front-load every prompt with the same five things, in the same order, every time.
Every prompt in this pack is built on the same structure:
This isn't a stylistic preference. It's how AI builders actually read a prompt. The early elements anchor everything below. Skip COMPONENT and you get a guess at what you wanted. Skip CONTENT and the model fills in lorem ipsum. Skip TECHNICAL and you get a Next.js answer when you asked for Vite.
[BRAND_NAME], [PRIMARY_COLOR], [PRODUCT_DESCRIPTION] mark exactly what to customize.Use the prompts and what they generate in unlimited personal and client projects. No attribution required. You just can't resell or republish the pack itself. Full terms in LICENSE.txt inside the download.
This is v1.0. As builder behavior evolves and new patterns emerge (and they will), you get the updates.
v0 by Vercel, Lovable, Bolt.new, and Cursor. Each prompt is tagged with its compatibility — most work across all four with no edits. The few that don't (typically whole-page landing prompts) are clearly tagged.
Every prompt specifies Component + Layout + Visual + Content + Technical, in that order. This structure consistently produces production-ready UI on the first generation instead of the vague output you'd otherwise have to re-prompt three times. It's not stylistic — it's how AI builders actually read a brief, from top to bottom, with the early elements anchoring everything below.
Yes. The pack ships as PDF, Markdown, JSON, and a Notion-ready CSV (with columns for Title, Category, Compatibility, Prompt, WhenToUse, Tags). Drop the CSV into a Notion database and you have a fully searchable prompt library in 30 seconds. The JSON is also ready to pipe into any internal tool or extension.
Both. Every prompt has clearly marked [PLACEHOLDERS] for things only you know — brand name, primary color, product description. Fill those in and the prompt works as-is. The rest of the prompt is engineered to run without edits.
Yes. The license covers unlimited personal and client project use — both of the prompts themselves and the UI they produce. You just can't resell or publicly republish the pack as a product, swipe file, or lead magnet. Full terms are in LICENSE.txt inside the download.
Yes. Prompts reference current patterns — Next.js 15 app router, Tailwind v4, shadcn/ui, lucide-react, motion (formerly framer-motion), @tanstack/react-table, @dnd-kit. Where a prompt assumes a specific library, the TECHNICAL line says so explicitly so you can swap it for your stack.
Yes — future v1.x revisions are included. As builder behaviors evolve (and they do, fast), updated prompts ship into your account.