10 prompts to get AI to build a website that really works
Ten copy-ready prompts, from a shop page and a portfolio to a survey, a stock system and a mobile app API, that end with your AI deploying to BrewInTH.
Many people open an AI chat, type "make me a coffee shop website" and get one good-looking page. Then the trouble starts: the form goes nowhere, nothing is saved, the layout breaks on a phone, and it is not clear how to get the site online.
Most of the time the AI is fine; the prompt just leaves too much out. This article collects 10 example prompts, from a one-page shop site to an API for a mobile app. Each one says what the site must do and which data it keeps, and ends by asking the AI to put it on BrewInTH and check it live. Copy one, change the details and use it right away.
In short
✅ A prompt that produces a working site has five parts: who it is for, the pages it needs, the data it keeps, the technology, and the deploy-and-check step
✅ Sites that only show information can be static; sites that take input from people need an app and a database
✅ Paste BrewInTH's Ready-made message for your AI before the prompt and the AI deploys by itself until you have a link
✅ Use an AI on a computer (Claude Code, Codex, Cursor…), because it has to create files and upload them
✅ Every prompt ends with the AI opening the live site to test it, not just "the build passed"
What a good prompt contains
- Who the site is for and what it does — for example "coffee shop customers who want the menu and opening hours on their phone". Say which language it should be in.
- The pages and buttons it needs — as a list. The clearer it is, the fewer rounds of fixes.
- The data it keeps and who can see it — for example sign-up names and phone numbers, visible to the owner behind a password.
- Technology and database — if you are not sure, "pick something BrewInTH supports" is fine.
- Deploy and check — ask the AI to put it online, open the real site, try every important button and give you the link.
Before you prompt: set up the project on BrewInTH
- Sign up and create a project. For the technology you can pick Let the platform decide: BrewInTH looks at the code on the first release and picks it.
- On the project page, press Create the AI link and token (automatic) and copy the Ready-made message for your AI.
- Open your AI tool on your computer in an empty folder, paste the ready-made message first, then one of the prompts below.
Every prompt has a line (paste the ready-made message from BrewInTH here); replace it with what you copied. The Free plan includes one project, which is enough to try them one at a time.
10 example prompts
1. A one-page site for a shop or business
(paste the ready-made message from BrewInTH here)
Build a one-page site for "Baan Doi" coffee shop, for customers who find it on their phones.
- Header with the name, a tagline and two buttons: "Call us" and "Open the map"
- Six signature drinks with prices, opening hours, the address and a LINE link
- A static site (HTML/CSS/JS), no database, fast on mobile
Then deploy it to BrewInTH, check the live site at phone width and send me the link.2. A portfolio or online résumé
(paste the ready-made message from BrewInTH here)
Build a portfolio site for a graphic designer in Thai and English, with a language switch.
- Home: a short intro, skills and a button to download my résumé PDF
- Eight projects in a grid; clicking one shows a large image and a description
- Contact: email and social links (no form)
Static site with placeholder images; name the files so I can swap the pictures myself.
Then deploy it to BrewInTH, check the live site and send me the link.3. A sign-up page that collects leads
(paste the ready-made message from BrewInTH here)
Build a sign-up page for a photography workshop.
- Details, date, time and price, plus a form: name, phone, email
- Validate the form, refuse a phone number that already signed up, show a thank-you page
- A password-protected /admin that lists sign-ups and downloads them as CSV
- Node.js with PostgreSQL; keep the admin password in the app settings, never in the code
Then deploy it to BrewInTH, sign up once for real and check it shows in /admin.4. A restaurant menu for QR codes
(paste the ready-made message from BrewInTH here)
Build a restaurant menu that guests open by scanning a QR code at the table, in Thai and English.
- Sections: single dishes, sharing dishes, drinks, desserts, with photos, prices and "spicy" / "vegetarian" badges
- The section bar sticks to the top while scrolling; text is easy to read on a phone
- Keep all items in one menu.json file so I can change prices myself
- A static site; after the deploy, create a QR code image that points to the live address
Deploy it to BrewInTH, check the live site and send me the link and the QR image.5. A survey or quiz that stores answers
(paste the ready-made message from BrewInTH here)
Build an 8-question customer satisfaction survey in Thai.
- 1-5 rating questions and a comment box, one question at a time with a progress bar
- Save answers to the database; do not collect names or phone numbers
- A password-protected /admin with the average score per question as a chart, plus CSV download
- Python FastAPI with PostgreSQL
Then deploy it to BrewInTH, answer it twice and check the chart in /admin is right.6. A news site or blog with an admin area
(paste the ready-made message from BrewInTH here)
Build a news site for a school parents' association with Laravel and MySQL.
- Home with the latest news and cover images, an article page and search
- An admin area where 2-3 editors log in to write, edit and delete news and upload images
- Uploaded images go to the persistent /data storage so a new release does not lose them
- Migrate with the release command php artisan migrate --force
Deploy it to BrewInTH, create the first editor account and tell me how to log in.7. An in-store stock system
(paste the ready-made message from BrewInTH here)
Build a stock system for a farm-supply shop, used internally by three people.
- Login on every page; two roles: owner (everything) and staff (stock in / stock out)
- Product list, quantity on hand, low-stock warnings and an in/out history
- Search by name or product code; usable on a phone
- Node.js with PostgreSQL; design the tables sensibly
Deploy it to BrewInTH, create one owner account and test one stock-in and one stock-out.8. A booking site
(paste the ready-made message from BrewInTH here)
Build a booking site for a massage shop open 10:00-20:00 every day, 60-minute slots, 3 therapists.
- Customers pick a service, a day and a free time, enter name and phone, and see a confirmation page
- At most 3 bookings per slot, never double-booked, Thai time
- A password-protected /admin that shows the day's bookings and can cancel one
Deploy it to BrewInTH, book from a phone and check that full slots cannot be picked.This one has a full walk-through with a test checklist in Build a booking website with AI.
9. A small web game
(paste the ready-made message from BrewInTH here)
Build an animal memory-match game for primary school children, in Thai.
- Three levels: 4x3, 4x4 and 6x4 cards, with a timer and a move counter
- Playable by touch on a phone, with a sound on a match (can be muted)
- Keep the best score on the player's device; no database
- A static site (HTML/CSS/JS), as small as possible
Deploy it to BrewInTH, play one level to the end on the live site and send me the link.10. A backend API for a mobile app
(paste the ready-made message from BrewInTH here)
Build a REST API for an income-and-expense mobile app with Node.js and PostgreSQL.
- Sign up / log in with email and password; API calls use a token
- Add, edit and delete entries and get a monthly summary; users only see their own data
- GET /health answers 200 and is set as the project's health path
- Every secret (such as the token signing key) lives in the app settings
Deploy it to BrewInTH, test every endpoint with real requests and give me short API notes.Add-ons that fit at the end of any prompt
- "Ask me first if something is missing" — the AI asks instead of guessing.
- "Never put passwords or API keys in the code; use the app settings" — secrets live in the project's App settings tab.
- "If the deploy fails, read the log and fix it until it works" — the AI can read the release log itself.
- "Test it at phone width too" — most visitors arrive on a phone.
- "Tell me what is left for me to do" — such as real photos or a custom domain.
Watch the video
▶ From a new project to a live site (1:30, in Thai)
Watch on YouTube
FAQ
Can I use ChatGPT or Gemini in a phone app?
The build-and-upload step needs an AI that works with files on a computer, such as Claude Code, Codex, Cursor or Windsurf. Checking status, setting up a domain and changing settings all work from a phone.
Do I have to pick the technology myself?
No. Choose Let the platform decide when you create the project, and BrewInTH picks from the code in the first release: a package.json means Node.js, a lone index.html means a static site.
Which sites need a database?
If the site must remember what people enter — sign-ups, answers, bookings, stock — it needs a database. If it only shows what the owner wrote, a static site is enough. See choosing a database.
How do I keep improving the site?
Continue in the same chat, say what should change and ask for a new deploy. If the token has expired, create a new link and token on the project page and paste it to the AI.
Can I write the prompt in Thai?
Yes. Current AI tools understand Thai well; mix in English names of technologies and commands as you like.
Summary
A prompt that ends in a working site covers five things: who it is for, the pages, the data, the technology, and deploying and checking. Pick the example closest to your idea, change the details, paste it after BrewInTH's ready-made message and let the AI work until you have a link that really works.
Start your first project free →