App builders · guidance updated 4 Oct 2026
Bolt.new prompt guide
Bolt offers two agents, Standard (fast and token-efficient, free) and Max (deeper reasoning, paid). Bolt picks the underlying models and doesn't publish them, so write prompts that don't depend on a particular model.
How to prompt Bolt.new
- State the app's purpose, users and core features first, written as a blueprint.
- Set the architecture up front: framework, styling, backend or database and any integrations.
- Have the first prompt build only the skeleton and one core feature, then add features one prompt at a time.
- Make one change per prompt, check it works, then move on to the next.
- Name exact files, components, classes or functions to change, and say what must not change.
- Use Plan mode to agree an approach or debug, then press 'Implement this plan' to build.
- Ask for error handling and logging from the start so you don't end up in token-burning fix loops.
- Describe the UI concretely: layout, palette, components and responsive behaviour.
- Point the user to Knowledge (account, project or team) or skills for rules that should apply every time.
- Suggest the Max agent only for large or complex refactors; Standard is enough for most UI work.
The shape of a good prompt
[App purpose and users] [Tech stack: framework, styling, backend] [Core features for v1, max 3] [This step: what to build now] [UI and design: layout, palette, components] [Data model] [Error handling and logging] [Out of scope / don't change]
Avoid
- Long lists of features and requirements in a single prompt
- Vague edits that don't name the file or element
- Clicking 'fix' over and over in an error loop instead of switching to Plan mode
- Using prompts for things built-in buttons do (publish, version history)
- Letting the chat context grow huge without clearing it
Example
Request a habit tracker app
Build a habit tracker web app for individuals who want to build 3-5 daily habits. Stack: React + Vite + TypeScript, Tailwind CSS, Supabase for auth and data. Step 1 only: project setup, email/password login, and a 'Today' screen listing my habits with a checkbox each. Don't build stats or reminders yet. Data: habits (id, user_id, name, colour, created_at), completions (habit_id, date). UI: single-column mobile-first layout, white cards on a light grey background, one accent colour per habit, large tap targets, an empty state with an 'Add your first habit' button. Add clear error messages and console logging around all Supabase calls.
