Ready-made prompts to copy
Starting an app
The first request you send to the tool. The clearer it is, the less rework later.
First request template for any app
When to use: At the very start, when you have the idea and nothing built yet.
I want to create a simple app for [who will use it], which is for [the main task, in one sentence].
It needs:
- [first thing, for example "a form to add customers"];
- [second thing, for example "a list of the customers added"];
- [third thing, if any].
For now it doesn't need [what's left out, for example "login, payments and sending email"].
The app will be used mostly on [phone or computer]. Use a clean look that's easy to understand. All the text should be in English.Three items in the list is plenty to start with. You can add the rest later, one request at a time.
Ask for a plan before building
When to use: When the idea is still fuzzy or you don't know if it fits in a small app.
Before writing any code, I want to talk through the idea.
My idea: [describe it in your own words, however it comes out].
Answer me in plain English, without technical terms:
1. What would be the simplest possible version of this app that already solves the main problem?
2. What should I leave for later?
3. Which parts could be more work or need extra care?
Don't build anything yet. I just want the plan.Some tools have a mode for chatting without changing the project. If yours does, use it with this prompt.
Introduction page for a small business
When to use: When you need a simple page that introduces a business and leads customers to get in touch.
Create a one-screen page for my business: [name and what it does, for example "Ana's Studio, clothing repairs"].
The page should have, in this order:
- the business name and a short sentence saying what we do;
- a list of services: [service 1], [service 2], [service 3];
- opening hours: [hours];
- a big "Message us on WhatsApp" button that opens a chat with the number [phone number with area code].
Don't invent prices, testimonials, numbers or awards. If any information is missing, leave a marked space for me to fill in.
Plain look, easy to read on a phone, text in English.The sentence “don’t invent prices, testimonials, numbers or awards” matters. Without it, the AI tends to fill the page with sample information that looks real.
Changing what already exists
Small, specific requests that touch one part without breaking the rest.
Change one thing without touching the rest
When to use: Whenever you want to change a detail of something that already works.
I want to change just one thing: [describe the change, for example "the Save button should be green"].
Where it is: [the screen or part of the app, for example "on the new order form"].
Don't change any other part of the app. When you're done, tell me in one sentence what you changed.Add a new feature
When to use: When the basics already work and you want the app to do one more thing.
The app already works the way I want. Now I want to add one thing: [the new feature, for example "a search box on the customer list"].
How it should work, from the point of view of the person using it: [describe what the person does and what they see, for example "they type part of a name and the list shows only the people with that name"].
Keep everything that already exists working as it is. If the change requires touching other parts, tell me before and explain why.Go back to how it was
When to use: When the last change made the app worse and you want to undo it through the conversation.
The last change made the app worse. Before it, [what worked, for example "the list showed all the orders"]. Now [what happens, for example "the list is empty"].
Undo the last change and put the app back the way it was before it. Don't try to fix it another way for now. Then tell me what was undone.If the tool has a version history, going back through it is usually safer than asking in the conversation. Use this prompt when you can’t find that option.
Improving the look
Colors, wording, phones and accessibility, no design skills needed.
Make the app easy to use on a phone
When to use: When the app looks good on a computer but is cramped or cut off on a phone.
The app will be used mostly on a phone. Adjust the layout for small screens:
- nothing can be cut off or require scrolling sideways;
- buttons big enough to tap with a finger;
- text readable without zooming in;
- forms with one field below the other.
Don't change colors, text or how the app works. Only the layout on the screen.To check, most tools have a button to see the preview at phone size. Opening the published link on your own phone is the most reliable test.
Change colors and style all at once
When to use: When the look is generic and you want it to match your business.
I want to change the look of the app to match [the business or the mood, for example "a cozy, simple, handmade bakery"].
Use [the color, for example "chocolate brown"] as the main color and keep the background light.
The text must stay easy to read, with good contrast.
Don't change the text, buttons or how the app works. Only colors, fonts and spacing.Review the app's text
When to use: Before showing the app to anyone. Typos and leftover placeholder text make it look careless.
Review all the text people see in the app: titles, buttons, messages, warnings and example text inside fields.
- Fix spelling and grammar mistakes.
- Rewrite any placeholder text, like "Lorem ipsum" or "Sample text", into real wording.
- Keep sentences short and direct, as if talking to a customer.
Show me a before and after list of what you changed. Don't change how the app works.Make the app accessible
When to use: So more people can use the app, including people with low vision or who use a screen reader.
Review the accessibility of the app and fix what needs fixing:
- enough contrast between text and background;
- every image has a text description;
- every form field has a visible label;
- the whole app can be used with just the keyboard;
- buttons have names that say what they do, instead of "Click here".
Explain in plain English what you changed. Don't change the look beyond what's needed.Saving information
When the app needs to remember things: lists, sign-ups, logins.
Save your data online
When to use: When the app needs to show the same information on different devices or to different people.
Right now the app saves data only on the device of whoever uses it. I want the information saved online, so I can see the same [orders, customers, tasks] on my phone and on my computer.
Before making any change, explain to me in plain English:
1. Which database option you recommend, preferably one the tool already offers.
2. Whether I'll need to create any account or do any setup outside of here.
3. How to make sure only I can see this data.
Wait for my confirmation before starting.This is one of the steps where the most things can go wrong, which is why the prompt asks for an explanation first. If the app will store other people’s data, first read about the personal data exposed error.
Ask for a login screen
When to use: When each person should see only their own information, or when only you should have access.
I want the app to have a login. Only people who log in can see and change [what should be protected].
Who will log in: [only me / my customers / my team].
Each person should see [only their own data / everyone's data].
Use the login option the tool itself offers, if there is one. Before starting, tell me what will change in the app and whether I need to set anything up outside of here.Login touches security. When it’s done, test with two different accounts and check that one can’t see the other’s data.
Understanding what the AI did
Ask for explanations in plain language before you move on.
Explain what you built
When to use: After the app works, to understand what was built and be able to ask for better changes.
Explain how this app works, as if I had never coded.
- What are the main parts and what does each one do?
- Where is the data stored?
- What happens, step by step, when someone uses the main feature?
Use everyday comparisons and avoid technical terms. If you need to use one, explain what it means.Make this request from time to time. Understanding your own app helps you write better requests and notice when something is wrong.
What could go wrong?
When to use: Before showing the app to more people, especially if it stores other people's data.
I'm going to share this app with [who will use it]. Review it and tell me, in plain English:
1. Can anyone see or delete data they shouldn't?
2. Is there any password, key or secret information visible in the app?
3. What happens if someone fills in a field wrong, leaves it blank or types a huge piece of text?
List the problems from most serious to least serious. Don't fix anything yet. I want to understand first.This review is not a substitute for one by a security expert. It helps you find the most obvious problems. If the app handles payments or sensitive data, get professional help.
Something went wrong after using a prompt? See what to do when you hit an error. Don’t know a word? Look it up in the glossary.
Frequently asked questions
Can I use these prompts in any tool?
Yes. They are written in everyday language, with no commands specific to one tool, and they work in Lovable, Bolt, Replit or any other tool that takes text requests.
Do I need to write prompts in a special way?
No. Write the way you would explain the task to a person. Being specific matters more than sounding technical.
What do I do with the parts in brackets?
Replace them with your own details. Where it says [type of business], write “hair salon”, for example. Delete the brackets. The more concrete you are, the better the result.
Why does the same prompt give different results?
Because the AI doesn’t answer the same way every time, even with the same text. If the result isn’t good, ask for changes instead of starting over.