Skip to main content

Do this

Be specific about data fields

Specify field types when it matters

Common field types to specify:
  • 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

Why: Gainable doesn’t know what features you want from those products. Describe the specific features you need.

Don’t use vague design terms

Don’t request everything at once

Don’t assume Gainable knows your domain


Changing an app you have already built

Everything above is about the prompt that creates an app. Once it exists, the rules shift: you are naming things that are already there, and a plan card appears before anything changes.

Changing a built app

Naming pages and components, bug versus preference, screenshots, and the plan card.

Quick reference

Learn more

Changing a built app

Prompting once it’s up and running

Examples

See real prompts in action

Common patterns

Templates for common app types