Use these prompts when you want Bolt.new to create a buildable app structure, not just a pretty first screen.
Start with a full prompt, then use the follow-ups to improve copy, layout, SEO, and conversion.
Create an MVP with routes, UI states, and product flow.
Build a SaaS MVP for [idea]. Include marketing homepage, auth screens, dashboard, settings, billing placeholder, onboarding checklist, sample data, and responsive styling. Keep the architecture simple and explain the file structure before implementation.
Generate a store flow from homepage to checkout mockup.
Create an ecommerce website for [product category]. Include homepage, category grid, product cards, product detail page, cart drawer, checkout mockup, reviews, trust badges, and responsive navigation. Use clean product photography placeholders and conversion-focused copy.
Build a practical admin app interface.
Build an internal tool dashboard for [workflow]. Include login placeholder, sidebar navigation, records table, detail panel, create/edit form, filters, activity log, and settings. Use a dense but readable operations interface.
Ask for routes, states, sample data, and constraints. Bolt prompts work better when the desired app behavior is included with the visual design.
After the first generation, ask Bolt to simplify the architecture, remove unused complexity, and make the primary user flow work end to end.
Include the app goal, routes, user flow, required components, sample data, and the level of functionality expected in the first version.
These prompts are designed to create strong first drafts. You should still review code, simplify structure, and test the main flow.