Copy-paste Bolt.new prompts for landing pages, SaaS dashboards, pricing pages, onboarding and AI apps, each paired with a design template so Bolt builds a page that looks professional.
Bolt builds fast, so the first prompt decides almost everything. These Bolt prompts list the page, the sections and the design rules in one go, and each one is paired with a BrowserMoon template you paste in, so Bolt ships a page that looks designed instead of a default layout.
How to use these Bolt prompts
1
Pick the prompt for your page
Choose the Bolt prompt for the page you are building, from a SaaS landing page to a login screen or an AI chat app.
2
Copy the template it uses
Each prompt is written to go with the template shown on its card. Copy that template, or any template from the Bolt templates page.
3
Give Bolt the design
I have pasted a BrowserMoon design template below. Treat it as the design system: match its fonts, spacing, colours, corner radius and components exactly, and only change the copy and content.
4
Fill in the brackets and send
Replace the parts in brackets, like [product name] and [audience], with your own details. The prompt ends with: “Build the whole page in one go, then list what you built and what is still placeholder.”
Which Bolt prompt to start with
Start with the hero section prompt if you only need a page to collect signups, or the SaaS landing page prompt for a full marketing site. Bolt does its best work on the first run, so put the whole page in that first message and add more pages afterwards.
Why Bolt needs a design in the prompt
Bolt.new writes a full React and Vite project from one message and shows it running straight away. Speed is its strength, but it means Bolt fills any gap in your prompt with its own default choices, and those defaults are the reason so many Bolt sites look alike.
These prompts leave no gaps. Each one lists every section, sets the design rules and points Bolt at a BrowserMoon template to match. Bolt then spends its run on building your page instead of guessing at fonts, colours and layout.
What is inside every Bolt prompt
Each prompt on this page is built from the same five parts. The page-specific part changes per prompt; the rest is written for how Bolt works.
1. What to buildThe product, the audience and the outcome the page must deliver, in one or two sentences.
2. Every section, in orderEach section named with what goes in it, so nothing is left for the tool to invent.
3. The designI have pasted a BrowserMoon design template below. Treat it as the design system: match its fonts, spacing, colours, corner radius and components exactly, and only change the copy and content.
4. The design ruleskeep one accent colour, use the template's type scale and spacing exactly, give every section generous white space, keep body text at least 15px, and make every layout work at 375px wide with no horizontal scroll.
5. The stack and how to finishBuild it with React, Vite and Tailwind CSS. Build the whole page in one go, then list what you built and what is still placeholder.
Tips for writing Bolt prompts
Say everything in the first prompt
Bolt does its best work on the first run. Put the page, every section in order, the design template and the design rules in your opening prompt.
Use the enhance button carefully
Bolt's prompt enhancer can rewrite your design rules away. Check that the template and the rules are still in the prompt before you send it.
Fix with small prompts
After the first version, change one thing per prompt. Big rewrite prompts make Bolt drift from the design.
Lock the design
If Bolt starts changing styles, tell it: keep the existing design, only change the content.
What to ask Bolt after the first prompt
Add a pricing page that reuses the header, footer and buttons from the home page.
Connect Supabase and save the signup form to a waitlist table.
Make every section work at 375px wide and fix any horizontal scrolling.
List every placeholder still on the page so I can replace it.
Common Bolt prompt mistakes
Letting the prompt enhancer rewrite your rules
Bolt's enhance button often drops design instructions. Check the template and rules are still there before sending.
Building on a broken first version
If the first run looks wrong, start a new project with a better prompt instead of fixing it message by message.
Running out of tokens on fixes
Big follow-up prompts rewrite whole files. Ask for one change per message to keep token use low.
Forgetting the mobile layout
Bolt previews at desktop width. Always ask it to check the page at phone width.
Who these Bolt prompts are for
Bolt is where many people build their first site with AI: indie hackers, students, freelancers and small teams who want a working page in minutes. These Bolt prompts are for anyone who has built something in Bolt that works but looks generic, and wants the next project to look like a funded startup's site.
More templates for these Bolt prompts
A prompt says what to build; a template shows Bolt what it should look like. These templates also fit the prompts above.
One that names the product and page, lists every section in order, and pastes a design template to follow. Bolt builds the whole page from the first prompt, so the more complete it is, the better the result.
How do I make Bolt websites look better?
Give Bolt a real design. Paste a design template into your prompt and tell it to match the fonts, spacing and colours exactly. That fixes the generic look most Bolt sites have.
Should I use Bolt's prompt enhancer?
Use it for ideas, then check the result. It can drop the design template or your rules. These prompts are already complete, so you can send them as they are.
Can these prompts build a full app in Bolt?
Yes. Start with the landing page or dashboard prompt, then use the login, onboarding and settings prompts to add the rest of the app one page at a time.
Do these prompts work on Bolt.new and Bolt for teams?
Yes. The prompts are plain text, so they work on any Bolt plan. Teams can share one prompt and template so every project starts with the same design.
How do I save tokens in Bolt?
Send one complete prompt first, then small, specific follow-ups. A good first prompt is the biggest token saver because Bolt does not have to rebuild the page.