Skip to main content

Prompting guide

You build with Berrybell by describing what you want. The clearer your description, the closer the result. This guide covers the habits and patterns that get the best output.

The core idea​

Think of the AI as a fast, capable builder who does exactly what you ask — so say what you mean. Vague requests get generic results; specific requests get the app you pictured.

❌ "Make a website for my business."

✅ "Build a one-page site for Bloom, a florist. Sections: a hero with a photo and a 'Order flowers' button, a grid of six bouquets with prices, an about section, and a contact form. Warm, elegant style with cream and sage colors."

Patterns that work​

Be specific about structure​

List the pages and sections you want, and what goes in each. The AI can fill in details, but it builds what you describe first.

Describe the goal, not just the look​

Tell the AI what a feature is for: "a signup form that saves the email to a database and shows a thank-you message" is far more useful than "add a form."

Work in small steps​

For anything non-trivial, make one change at a time and check the preview before the next. Small steps are easier to get right and easier to undo.

Reference what's on screen​

Point at the preview: "make the hero image full-width," "the pricing cards should be equal height," "move the testimonials above the footer."

Give examples and constraints​

"Like a Notion-style sidebar," "keep it to two colors," "mobile-friendly," or "no stock-photo look" all steer the result.

When you have the real material, hand it over instead of describing it:

  • Paste the link. "Use the booking API documented at https://… to show live availability" works because the AI can read a page you link to, and the prompt says what the link is for. It can't search the web, so give it the address rather than asking it to look something up.
  • Attach the real thing. "Use the attached logo in the header" puts your actual file on the site. A screenshot says "make it look like this" faster than any description.
  • Describe the images you want generated. "A warm hero photo of a florist's counter" is enough. Each generated image is billed, and the AI can make up to four per message, so say "no generated images" if you'd rather it didn't.
  • Say what a link is for. Berrybell also treats the first two links in any message as sites to mirror (the Logs tab shows Reading reference site…). The AI gets their structure and style: the sections, headings, navigation, buttons, colours and fonts, but not the body text. When a link is only there for its content, like API documentation, say so, for example "don't copy its design". If you want a site's text adapted, ask for that explicitly, and only reuse wording (headings and button labels included) that you have the right to use.

See Reference a site and Images & attachments.

Fixing and refining​

  • When something's wrong, describe what is wrong and what you expected: "the menu overlaps the logo on mobile — it should stack below it."
  • When something breaks, tell the AI what you did and what happened; it will work on a fix.
  • To change direction, just say so — "actually, make this a dark theme."

Adding functionality​

Prompt for capabilities the same way you prompt for pages:

  • "Add a database to store bookings, with fields for name, date, and party size." → Databases
  • "Let customers pay for the Pro plan with a card." → Stripe payments
  • "Send me an email when someone submits the contact form." Berrybell sends this itself, as a notification to you, on every plan. An admin turns on Notifications to you under Cloud → Email, and then you publish. → Notifications to you
  • "Email customers a confirmation when they place an order." The AI drafts an email template, and Berrybell checks it before it can send. Emails to customers need a paid plan and a sending domain. → Your email templates, Sending email from your domain
  • "Send a monthly newsletter to my subscribers." Newsletters and other marketing email need your own email provider, for example a Resend API key stored as a secret. → Variables & secrets

A quick checklist​

Before you send a prompt, ask yourself:

  • Did I say what to build and what it's for?
  • Did I describe the key sections or fields?
  • Is this one focused change, or should I split it up?
  • Did I mention any style or constraints that matter?

Next steps​