A pinned dependency list
The spec names the framework, styling approach and backend and forbids extras, keeping the WebContainer install small and fast.
TheMegaPrompt
Vision → gap analysis → ROI → stack → Mega-Prompt
The ultimate PRD & Mega-Prompt generator for Bolt.new
Five guided steps produce a Bolt-ready PRD for web apps and landing pages: chosen stack, data model, feature list and hard constraints, so the first generation compiles instead of thrashing.
LovableBolt.newCursorBase44Trusted by 200+ app builders
Build SaaS apps, web applications, landing pages, and custom websites using Lovable, Bolt.new, Cursor, and Base44.
Step 1 of 5 — Vision20%
Step 1 — Your product vision
Describe Your App, Website or Landing Page Idea
Plain words are perfect — no technical language needed. Who is it for, what do they do, and what should the first version of your app or website include?
Prompt qualityNothing yet
Start with one sentence: who is it for and what do they do with it? (0 words)
Smart defaults (saves build credits)
These are AI recommendations read straight from your description — adjust them only if something looks wrong. Anything you write later in the text always wins over these switches.
Making money (is this a paid product?)
Free / internal tools skip payments entirely and stay on $0/mo free tiers.
Write a couple of sentences about your idea to unlock the next steps.
How TheMegaPrompt builds PRDs and architecture specs for Bolt.new web apps and landing pages
Bolt writes an entire project in one pass, so the opening message decides whether the preview compiles. TheMegaPrompt produces that message: pinned stack, typed data model, ordered screens and hard constraints for your app or website.
Data model before screens
Typed entities are defined first, so generated pages read fields that actually exist instead of crashing on undefined.
Screen-by-screen build order
Each screen is described with its purpose, data and actions, which is how Bolt produces a coherent app or website rather than disconnected pages.
Realistic seed data, no placeholders
The prompt bans lorem text and stub components, so the first preview is something you can actually judge.
How to use a structured PRD with Bolt.new
Bolt writes the whole project into a browser runtime in one pass. When the prompt is vague it invents dependencies and half-wired files, and the preview fails with import or runtime errors before you can review anything. A detailed PRD keeps apps and websites on track.
1. Pin the stack and dependencies
Bolt installs whatever it decides it needs. Naming the framework, styling approach and backend keeps the dependency tree small and the install step fast.
- State the framework, styling library and backend explicitly.
- Say 'no extra dependencies beyond the ones listed'.
- Call out environment variables rather than leaving them to be invented.
2. Describe the data model before the screens
Screens generated ahead of a defined data shape end up reading fields that never exist — the classic undefined-property crash in the preview.
- Provide tables or entities with typed fields.
- Define which reads are public and which require a session.
- Include realistic seed data expectations, not lorem placeholders.
3. One paste, then targeted fixes
Paste the full Mega-Prompt as the opening message. When something breaks, quote the exact error and the file rather than asking Bolt to 'fix the app' — broad requests trigger broad rewrites.
- First message: the complete PRD Mega-Prompt.
- On failure: paste the error text verbatim.
- Keep each follow-up scoped to a single file or feature.