Prompting tips

Floot is only as clear as your prompt. These four habits make the biggest difference.

Include enough context

Be specific and descriptive about what you want Floot to change. When something is broken, do not just say “it doesn't work” — describe what you did, what you expected to happen, and what actually happened.

Use the Select or Annotate tool to point at the exact element you mean. For example, select a Submit button and say:

When I click the Submit button, a dialog should open, but nothing happens.

That works far better than “that button doesn't work”.

Keep it focused

Ask for one thing per prompt. Bundling several changes together means you cannot verify any of them cleanly, and if something goes wrong you have to untangle which change caused it.

Don't use AI to write your prompts

Pasting a prompt written by ChatGPT or another AI usually backfires. Those prompts tend to be verbose and full of invented technical details that pull Floot in the wrong direction.

Write it yourself, in your own words. Use another AI to brainstorm or research if it helps — just avoid copying and pasting the result.

Better still, turn on Discuss mode and hash out the details with Floot directly. Floot knows your project and its own capabilities; an outside chatbot knows neither.

Describe outcomes, not implementations

Say what the app should do for the person using it. Naming specific libraries, frameworks, or database tricks usually constrains Floot for no benefit — it already knows the stack it is building on.