Do this
Be specific about data fields
Specify field types when it matters
- Currency: “amount (currency)” or “price in dollars”
- Date: “due date” or “close date”
- Percentage: “probability (percentage)”
- Options: “status (option A, option B, option C)”
- Yes/No: “is active (yes/no)” or “completed (checkbox)“
Describe relationships clearly
Request specific visualizations
Define options explicitly
Don’t do this
Don’t reference other products
Don’t use vague design terms
Don’t request everything at once
Don’t assume Gainable knows your domain
Updating existing apps
When modifying an app you’ve already built:Reference existing elements
Specify where to make changes
Build on what exists
Screenshot and annotate — your secret weapon
Sometimes words aren’t enough. Instead of trying to describe exactly what’s wrong or what you want changed, you can take a screenshot of your app and annotate it with drawings, arrows, and text to show the agent exactly what you mean.How it works
- Click the camera icon in the chat input toolbar

- Allow the browser to capture your current tab when prompted

-
The Annotate Screenshot editor opens — use the toolbar to:
- Draw freehand circles, underlines, or highlights
- Add arrows pointing to specific elements
- Add text labels explaining what to change
- Draw rectangles to highlight areas of interest
- Add a written description in the text field below the screenshot
- Click send to submit the annotated screenshot with your instructions

When to use it
- Something looks wrong — circle it and say “this should be blue, not red”
- Layout issues — draw arrows showing where elements should move
- Missing elements — point to where a button or field should appear
- Exact positioning — show precisely where you want a chart or component placed
Asking questions vs requesting builds
Gainable can answer questions about your project without making changes.To ask a question
To request a change
Recovery from mistakes
If something wasn’t built correctly:Be specific about what’s wrong
Describe what you expected
Quick reference
| Situation | Best Practice |
|---|---|
| Defining data | List all fields with types |
| Connecting data | Explicitly state relationships |
| Adding charts | Name the chart type and what data it shows |
| Adding features | Use feature names (kanban, chat, filter) |
| Styling | Reference theme names or specific colors |
| Updating | Reference existing elements by name |
| Fixing issues | Describe what’s wrong and what you expected |
Learn more
Examples
See real prompts in action
Common patterns
Templates for common app types