Guide · 6 min read

How to write prompts for an AI app builder: a practical guide with examples

By the ReasonateAI team ·

The quality of what an AI builds depends heavily on how you describe it. You do not need special tricks, just a clear structure. This guide gives you one you can reuse for any website or app, with examples of what works and what does not.

The five-part prompt structure

  1. What it is: the type of site or app and its name. "A landing page for FitTrack, a workout tracking app."
  2. Who it is for: the audience. "For busy professionals who work out at home."
  3. What it must contain: the sections or screens, in order. "Hero, features, how it works, pricing, FAQ, sign-up form."
  4. Real content: names, prices, contact details and key messages you already know.
  5. Style: colours, mood and references. "Modern and energetic, dark background, neon green accents."

A weak prompt vs. a strong prompt

Weak: "Make a website for my coaching class."

Strong: "Build a website for Bright Minds Coaching in Lucknow, which prepares Class 11 and 12 students for JEE. Sections: hero with a Book a free demo button, courses (JEE Main, JEE Advanced, Foundation) with duration and fees, faculty profiles, results with top ranks, timings, location with map, and an enquiry form. Style: trustworthy and clean, navy and orange."

The strong version tells the AI the audience, the sections, the real content and the look. The first result will be much closer to what you want.

How to ask for changes

  • Point to the exact place: "In the pricing section, make the middle card stand out."
  • One or two changes per message, so you can check each one.
  • Describe the outcome, not the code: "make the menu easier to use on phones" works well.
  • If a change goes wrong, say what you see: "the buttons now overlap on mobile, fix that".

Useful phrases

  • "Mobile-first": design for phones, then larger screens.
  • "Use placeholder images" when you will add your own photos later.
  • "Keep everything else the same" when you only want one change.
  • "Use React" or "use plain HTML, CSS and JavaScript" if you have a preference.

Common mistakes

  • Packing ten changes into one message.
  • Only describing style ("make it pretty") without content.
  • Leaving placeholder text in the final version. Always replace it with real details.
  • Starting over instead of refining. Small changes on a good base are faster.

Frequently asked questions

How long should a prompt for an AI app builder be?

Usually three to six sentences: what it is, who it is for, the sections, your real content and the style.

Should I write my prompt in English?

English works best today, but simple language matters more than perfect grammar.

What if the AI gets it wrong?

Describe what you see and what you want instead, one change at a time. Refining is faster than starting over.

More guides