Bolt.new Prompt Guide

A Bolt prompt instructs a system that can create files, pages and logic. Define the engineering boundary, not just the desired answer.

#Include six decisions

State the goal, stack, core features, data source, exclusions and acceptance criteria.

textCopy
Goal: build a simple booking prototype.
Stack: React + Tailwind.
Data: local mock data only.
Features: create booking, list bookings, cancel booking.
Constraints: no auth, no backend, mobile-first.
Acceptance: user can create one booking and see it in the list.

This gives you observable criteria after generation.

#Build in layers

Use the first round for structure and the main workflow, the second for data states and interaction, and the third for copy and visual polish. Reusable briefs are more controllable than a single oversized instruction.

#Why broad prompts fail

Requesting authentication, payments, administration, analytics, role-based dashboards and external APIs at once delegates information architecture, data flow, states and hierarchy without defining them. The resulting pages may not form a coherent workflow.

#Plan complex work first

textCopy
Do not write code yet.
First show the component breakdown, state flow, and files you plan to create.

Useful constraints include keeping the current folder structure, listing assumptions, showing affected files, making minimal changes and avoiding unrelated rewrites.

When the workflow and constraints are clear, generation is easier to assess. If the product is still undefined, request a structural proposal before a complete application.

#Related pages

• First app
• Deployment guide
• Bolt overview