Most AI prompt generators write prompts for chatbots or image models. This one writes the first prompt for an app: what it does, who uses it, its screens, what it saves, login and look. Then it gives you the next three prompts, in an order that keeps a new app from breaking.
Describe your app
Fill in what you know. The prompt below updates as you type. Nothing you type leaves your browser.
One or two sentences. This is the only field you need.
Separate them with commas.
1. Your first prompt
Build a web app. What it does: Lets a dog walker track which dogs they walked each day and send owners a short update. Who uses it: me, plus about 20 dog owners. Screens for this first version: - Today's walks - Dog list - Owner page Data it needs to save: dogs, owners, walks (date, time, notes, photo). Login: each person signs in with their own account and only sees their own data. Look and feel: friendly and colorful, with rounded cards, soft colors and big buttons. It should work well on a phone and on a computer. Start with the screens and realistic sample data. Don't connect a database yet. Keep it simple, and ask me before adding features I didn't list.
2. Then send these, one at a time
- 2
Connect a database and save dogs, owners, walks (date, time, notes, photo) for real. Replace the sample data and keep the screens the same.
- 3
Add sign up and log in with email and password. Each person should only see their own data. Add a log out button.
- 4
Go through every screen at phone width. Fix anything that overflows or is hard to tap, and add empty states, loading states and clear error messages.
How to read your prompt
The prompt has one line per decision, so you can see what the AI app builder will get and change any line before you paste it.
- What it does comes first because it's the line the builder leans on most. If you only fill in one field, fill in this one.
- Screens are a short list. With no screens, the prompt asks the builder to suggest three to five. That works, but you'll often get a screen you didn't want.
- Data it needs to save tells the builder which things to model, like "dogs, owners, walks". Name the things, not the tables. The builder picks the structure.
- Login is a yes, a no, or "skip it for now". Saying no out loud matters. If you don't, some builders add a sign-up page anyway.
- Look and feel turns one choice into a short design brief: colors, spacing, and what the buttons feel like.
- The last line asks for sample data first, no database yet, and a check-in before extra features. That's the line most hand-written prompts leave out.
If a line looks wrong, edit the field above and the prompt changes as you type.
Why the prompts come in this order
The generator doesn't call an AI. It fills in a fixed template with what you typed, in your browser. So the method is the order of the template, and here's the reasoning behind it.
- Screens with sample data first. The first version should be something you can click through in the preview. When the screens are wrong, you fix them in one short message. When the screens, the database and the login all arrive together, one wrong guess touches all three.
- Then the database. Once the screens look right, the follow-up asks the builder to save the same things for real and keep the screens as they are. In Dyad, that's when you connect Supabase or Neon (Neon works with Next.js and Vite projects).
- Then login. Sign-up and "each person sees only their own data" depend on the data being real. Asking for them after the database means the builder adds them to the tables it already made.
- Then a phone-width pass and a security pass, as many as fit in three follow-ups. They catch the problems people find in their first week: screens that overflow on a phone, missing empty states, and data one person can see that they shouldn't.
This follows the advice in Dyad's own chatting guide: be as specific as you can, most of all in the first prompt, so the AI builds what you mean instead of guessing.
What the generator can't do: it doesn't know your field, and it doesn't check whether your idea needs things like payments, maps or email. Add those as their own prompts once the basics work. It also writes web apps only. If you need a phone app in the app stores, read how to build a mobile app with AI first.
A worked example
The tool opens with this example filled in. A dog walker wants to track which dogs they walked each day and send owners a short update. Here's what they typed:
- What does the app do? Lets a dog walker track which dogs they walked each day and send owners a short update
- Who uses it? Me, plus about 20 dog owners
- Main screens: Today's walks, dog list, owner page
- What does it need to save? Dogs, owners, walks (date, time, notes, photo)
- Login: Yes, each person has an account
- Look and feel: Friendly and colorful
The first prompt asks for three screens with realistic sample data and no database yet. The follow-ups are, in order:
- Connect a database and save dogs, owners and walks for real, keeping the screens the same.
- Add sign up and log in, so each person sees only their own data.
- Go through every screen at phone width and fix what overflows.
That's four messages for a first working version, and each one is small enough to check in the preview before you send the next.
Using the prompt in Dyad
Dyad is a free, open-source AI app builder that runs on your computer. You can use your own API keys, a free local model, or your ChatGPT subscription. Here's how the prompt fits in:
- Download Dyad, create a new app and paste the first prompt as your first message.
- If you'd like to talk the idea through before any code is written, switch to Plan mode and paste the prompt there. Plan mode breaks a feature into steps and asks about details before it builds.
- Check the preview, then send the follow-ups one at a time.
- If a step goes wrong, restore the version before it. Every change the AI makes is saved as a version you can go back to.
The prompts aren't tied to Dyad. They work in any AI app builder you chat with. If you already planned your app in a ChatGPT conversation, turning that ChatGPT idea into an app shows how to bring the plan across. For more on writing prompts yourself, see the vibe coding beginner tutorial, and keep these prompts for fixing a vibe-coded app for when something breaks.
FAQ
How do I prompt AI to make an app?
Say what the app does, who uses it, which screens it has and what it needs to save. Then ask for the screens with sample data first, and add the database and login in later messages. The generator above writes that first prompt and the next three for you.
Is this prompt generator free?
Yes. There's no sign-up, and nothing you type is sent anywhere: the prompt is put together in your browser. You'll still need an AI model to build the app. In Dyad that can be a free local model, your own API key, or your ChatGPT subscription.
Does it work with ChatGPT?
The prompts are plain text, so you can paste them into ChatGPT and ask it to improve them. To get an app you can click through and keep building, paste them into an AI app builder.
What are the limits of an AI prompt generator?
It only knows what you tell it. A prompt can't make up for a vague idea, and it won't spot that your app needs payments or email. Treat the output as a strong first draft: read it, change what's wrong, then paste it.
What would you build first with it? Try the generator, and tell us how the first prompt went in the Dyad community on Reddit.
