Prompting guide
The best Cocoding AI prompts describe the product, workflow, data, and constraints. Avoid only asking for a visual page unless you really want a static prototype.
Prompt structure
Use this pattern:
Build [type of product] for [target users].
Users should be able to [main user actions].
Admins should be able to [admin actions].
The app needs data for [entities].
Include [integrations, authentication, payments, emails, uploads, reports].
Use [style or stack preference] if possible.
The first version is complete when [success criteria].
What to include
| Include | Why it helps |
|---|---|
| User roles | Helps the assistant separate public, customer, and admin screens. |
| Data objects | Guides database tables, forms, and relationships. |
| Workflows | Produces a usable app instead of disconnected screens. |
| Constraints | Keeps the result close to your business rules. |
| Example data | Makes preview and testing easier. |
Good follow-up prompts
- "Add a booking status workflow with pending, confirmed, cancelled, and refunded states."
- "Create an admin table for products with image upload, stock, price, and category."
- "Make the dashboard mobile responsive and simplify the top navigation."
- "Add sample seed data so I can test the preview."
Prompts to avoid
- "Make it better."
- "Build a marketplace."
- "Add everything."
- "Fix it."
When a result is wrong, name the exact screen, component, data field, or error message that needs attention.