Getting Started
Prompting Best Practices
Write clear prompts that produce better app output.
Good prompts are outcome-driven, specific, and easy to iterate on.
Why this matters
Prompt quality directly impacts app quality. A strong prompt saves time and reduces back-and-forth edits.
What you can do
- Write prompts that clearly define users, workflow, and expected outputs.
- Avoid vague requests that create unclear app structures.
- Improve your app through short, focused follow-up prompts.
Step-by-step guide
- Start with one business objective.
- Name the main users and what they need to do.
- List core data fields the app must track.
- Mention required actions such as notifications or approvals.
- Add constraints like "mobile-friendly" or "internal use only."
Example
Weak prompt
"Make an app for operations."
Strong prompt
"Build an operations request app where staff submit requests, managers approve or reject, and completed requests are archived. Include WhatsApp confirmation to requester."
Tips
- Prefer short sentences over long paragraphs.
- Ask for one major change per follow-up prompt.
- Use concrete words like "approve," "assign," "schedule," and "notify."
Common issues
- Vague prompts such as "make it modern" without business context.
- Prompts that mix many unrelated workflows in one request.
- Missing user roles, which causes access confusion later.