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].
Example first prompt
Build a booking management SaaS for small rental businesses.
Guests can search listings, view availability, request a booking, and pay.
Hosts can create listings, manage bookings, update availability, and review payments.
Admins can view all users, listings, bookings, payment status, and support notes.
Use PostgreSQL for users, listings, bookings, payments, reviews, and messages.
Include authentication, responsive dashboard pages, seed data, and clear empty states.
The first version is complete when I can preview the guest booking flow and host dashboard.
This style gives Cocoding AI enough product context to create connected screens, data models, and runtime behavior instead of a disconnected landing page.
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. |
Product detail checklist
Before pressing send, check whether your prompt answers these questions:
- Who signs in and what role do they have?
- What is the main object in the app, such as booking, invoice, lead, lesson, task, or product?
- Which screens are public, private, or admin-only?
- Which fields are required on each form?
- What status workflow matters, such as draft, pending, approved, paid, cancelled, or archived?
- What should appear on the dashboard?
- Which integration or database should be connected now, and which can wait?
- What should the preview demonstrate after the first generation?
Turn vague requests into buildable instructions
| Vague request | Better request |
|---|---|
| Build a marketplace. | Build a marketplace for local services with provider profiles, search, booking requests, reviews, and admin approval. |
| Add payments. | Add Stripe checkout for the Pro plan, store subscription status, verify webhooks, and show billing state in account settings. |
| Make the dashboard better. | Add cards for active bookings, monthly revenue, pending approvals, and recent customer messages. |
| Fix mobile. | On mobile, stack the booking form above the calendar, keep primary actions visible, and reduce table columns to key fields. |
| Add CRM. | Add contacts, companies, deals, pipeline stages, next follow-up date, and a notes timeline. |
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.
Use screenshots as context
When a visual layout matters, attach a screenshot and explain how to use it. Do not rely on the image alone.
Use the attached dashboard screenshot as layout inspiration only.
Keep our Cocoding AI-generated app focused on bookings, revenue, guests, and listing availability.
Do not copy private names, logos, or exact customer data from the screenshot.
Prompt review before generation
For larger projects, send a planning prompt first:
Before generating code, summarize the app architecture, main tables, pages, and risks.
Ask up to five clarification questions if something is missing.
Use this when the workflow includes payments, user roles, external APIs, complex permissions, or production handoff requirements.