Guides
How to write prompts that build better apps
The difference between a vague app and a useful one is usually the prompt. Practical patterns for describing people, data, rules and look to an AI app builder.
Kuika AI team4 min read
A good prompt for an AI app builder names the people who use the app, what they do, the information the app keeps and the rules it must follow. You do not need technical words. In Kuika AI, a prompt of four to six plain sentences is usually enough for a strong first version, and Plan mode lets you fix gaps before anything is built.
The four things every prompt needs
Think of the prompt as a short brief to a colleague who will build the app for you.
| Part | Ask yourself | Example |
|---|---|---|
| People | Who uses it, and in which role? | Residents, the building manager, technicians |
| Actions | What does each person do? | Report a problem, assign it, mark it done |
| Data | What does the app need to remember? | Requests, categories, photos, notes |
| Rules | What must always or never happen? | Only the manager assigns, residents see only their own requests |
Put them together and you get a prompt like this:
Build a maintenance request app for an apartment building. Residents report a problem with a category, a description and up to three photos. The building manager assigns each request to a technician and sets a priority. Technicians see their open jobs for today and mark them done with a note. Residents get an email when their request is done. Fill it with 30 sample requests from the last month.
Patterns that work
Use your own words for things. If your team says "work order", do not write "ticket". Kuika AI keeps the names you use for tables, columns and statuses, which makes the app feel like yours.
Give numbers. "Approval above 5,000 USD", "reminder 24 hours before", "40 sample customers across 3 cities". Numbers turn a vague request into a precise one. When you state a volume for sample data, Kuika AI fills related tables in proportion, so a demo looks real.
State the rules out loud. "A rejection needs a reason." "A booking cannot overlap another." Rules you do not write down are rules the app may not follow.
Say what is out of scope. "No sign-in, this is a personal checklist" is a valid instruction. Kuika AI adds sign-in to new apps by default, so say so if you do not want it.
Mention the look in one line. "Calm and professional, lots of white space" or "bold colors, made for a phone". You can choose a design system on the home page too.
Let Kuika AI help you
- Press "Enhance prompt". It rewrites your idea into a fuller brief that you can edit before sending.
- Use Plan mode. Kuika AI asks a few quick decisions about things you left open. Answer them or press "Decide for me".
- Attach what you already have. A screenshot, a PDF spec, a Word document or an Excel sheet. Kuika AI reads it and follows it closely when you ask it to build what the document describes.
- Talk instead of typing. The prompt box has voice input for when it is easier to explain out loud.
After the first version: one change per message
Once the app exists, small and clear requests work best. Compare:
- Weak: "Make the dashboard better."
- Strong: "On the dashboard, add a card with the number of open requests per category, sorted from most to least."
If a change is big, such as a new module, switch Plan mode on for that message. Kuika AI drafts a plan for the change, and nothing is touched until you press "Build this plan".
Add a monthly report screen for the building manager: number of requests per category, average time to close and the three technicians with the most closed jobs. Let the manager download it as a PDF.
For changes you can see, it is often faster to click than to type. Click Edit design in the preview, select the element and change it directly, or describe the change for just that element.
Give Kuika AI standing instructions
If you keep repeating the same preference, such as "always use 24-hour time" or "all prices are in euros", add it once under More › Knowledge. Kuika AI remembers it for every later change in that app.
Common questions
How long should my prompt be?
Four to six sentences is a good start. Cover the people, what they do, the data and the rules. You can always add more in later messages.
Do I need technical terms like database or API?
No. Describe your business in your own words. Kuika AI decides how to store the data and build the screens.
What if the result is not what I wanted?
Tell Kuika AI what is wrong in the chat, or go back to an earlier version from the version history. Starting with Plan mode on also helps you catch misunderstandings before anything is built.