Vibe coding prompts that work: how to get a good first build15 October 2026 · 3 min readTwo people can ask the same AI builder for "a booking app" and get very different results. The difference is rarely the model. It is what the prompt gave the model to work with.These are the habits that make the first build good and keep the tenth one good too. They work on any builder; the examples use SPOE.1. Write a brief, not a wish"Make me a booking app" leaves every decision to the model, so it makes the safest, blandest choice for each one. A brief makes those decisions for it.A good first prompt says:

Who uses it and what they need to do. "Customers pick a service, a day and a time slot, and book."

What the owner sees. "An admin page that lists the day's bookings and can cancel one."

The rules. "Slots are 30 minutes, 9am to 5pm, Monday to Saturday. No double bookings."

The look. "Calm and clean, white and sage green, like a day spa."

Here is the difference in practice:

A booking app for Serenity Day Spa in Glenelg. Customers choose a treatment (massage 60 min $120, facial 45 min $95, manicure 30 min $55), then a day in the next two weeks and a free 30-minute slot between 9am and 5pm, Monday to Saturday, and book with their name, email and phone. No double bookings. An admin page lists the day's bookings and can cancel one. Calm and clean, white and sage green.

That prompt gets you something close to finished. "A booking app" gets you a demo.2. Give it your real words and picturesBuilders fill gaps with filler: "Lorem ipsum", "Feature one", "Your company". Give them your name, prices, hours and phrases instead. Attach your logo, a photo of your shop or product, a screenshot of a page you like, or a spec document. On SPOE, pictures you attach are saved into the project and used in the design, and documents are read as material for the request.3. One change at a timeAfter the first build, ask for one thing per message: "Add a cancellation email", then "Show prices on the booking page", then "Make the calendar start on Monday". Small changes are easier for the model to get right and easier for you to check and undo.On SPOE you do not have to wait for each one: type the next request while a change is running and it waits in the queue, then runs when the one before it is done.4. Say what is wrong, and where"It's broken" gives the model nothing. "On the booking page, choosing a Saturday shows no slots, but Saturdays should have 9am to 1pm" gives it everything. Even better: on SPOE, click the part of the page you mean in the preview, and the builder gets exactly which element you are talking about.5. Set standing rules onceIf you keep repeating yourself ("Australian spelling", "prices in AUD with GST", "never use pure black"), make it a rule. On SPOE, type /remember and the rule, and every build follows it from then on. It is saved in a file in your project, AGENTS.md, so other AI coding tools read it too.6. Ask before you build bigFor a large app, ask for a plan first. SPOE's Agent mode splits a big request into steps you can read, edit and remove before anything is built, then builds them one at a time, each reviewed. Discuss mode lets you talk an idea through without changing a single file.7. Check the cost before you sendA clearer prompt is also a cheaper one: fewer rounds of "no, not like that". SPOE shows an estimate before you send, charges for what the build actually used, and never charges for a build that fails. If you are unsure your prompt is clear, the wand button rewrites it into a specific brief for a credit or two.Try itThe fastest way to learn is to write one good brief and see what comes back. Start free with 250 credits, no card, and use the spa prompt above as a template. Or browse app ideas for starting points.Pricing · Blog · App ideas · Compare builders · Verify an export · Developer API · Start freeThis page needs JavaScript to run the app itself. Everything above is a plain description of it.