- What this is
- The same seven steps for every app prompt: pick it, build it, test it with fake data, open the accounts, publish it, and check what real use needs.
- Who it is for
- Anyone who wants an app for their business and has never built one.
- What you will get
- A live app you built from a prompt, tested with fake data.
- Time
- About 70 minutes
- You need
- An app prompt from the Library
- A tool that builds projects
- About an hour
Your path: From the prompt to a live app
Pick your app prompt
Why: Each app PromptA prompt is the message you give an AI tool to tell it what you want. is a complete brief, so you do not start from a blank page.
Open the Library, then Prompts, and choose a goal under Build a real app.
What to do
- Open the Library and press the Prompts tab.
- Choose your app, answer the short questions, and press Make my prompt.
You should see: A long prompt with parts: Pages, Data tables, Security and Done when.
Stuck?
- I do not see my kind of app?
- Use Something else, or the closest app, and tell the AI what is different.
- It looks very long?
- That is normal. Long means fewer guesses.
From a prompt to a working app
- ☐ Pick your app prompt
- Open the Library and press the Prompts tab.
- Choose your app, answer the short questions, and press Make my prompt.
You should see: A long prompt with parts: Pages, Data tables, Security and Done when.
- ☐ Open a tool that builds projects
- Open Claude Code, Cursor or OpenAI Codex.
You should see: An empty project is open in the tool.
- ☐ Paste the prompt and answer its questions
- Paste your prompt in the tool and send.
- Answer each question, or reply with the word below.
You should see: The tool shows a short plan and waits for your go.
- ☐ Test every step with made-up data
- Run the command it gives you and open the page it names.
- Press Copy to get a test plan, and try each item.
You should see: Each page does what the tool said it would do.
- ☐ Open the accounts it needs
- Open the accounts guide and pick A booking or business tool.
- Follow the steps for each account.
You should see: A Supabase project and a Vercel account, and your secrets kept in environment variables.
- ☐ Put it online
- Follow the hosting guide to publish.
- Add each environment variable from your .env.example in Vercel.
You should see: A live link, with nothing secret visible in the page source.
- ☐ Before real customers use it
- Ask your accountant or lawyer about any rule that applies to your data or your money.
- Tell people what you keep and why, and keep as little as you can.
You should see: You know who can see the data, and where your own copy is kept.
Read the guide: Hosting: GitHub and Vercel