Prompting tips

Tips to write better prompts for Floot

Include enough context

Make sure your prompt is specific and descriptive about what you want Floot to change in your app.

When there's a bug, don't just tell Floot "it doesn't work". Give Floot more info!

Do this to describe your issue: describe what you did, what you expected to happen, and what actually happens.

To help Floot even more, you should also use the Select or Annotate tool to point out the exact UI element that's relevant (if applicable).

For example, imagine your app has a Submit button that isn't working. You could use the Select tool to select the button and say this:

"When I click the Submit button, a dialog should open, but it does nothing"

The above example will work much better than "that button doesn't work".

Keep it focused

Only tell Floot to do one thing in your prompt. Avoid bundling up multiple changes. You want to be able to verify the change afterwards before moving on to avoid having to look at multiple features.

For example - only ask for one feature, change, or fix per prompt.

Don't use AI to write your prompts

Using ChatGPT or another AI to write your prompt is usually a bad idea. AI-generated prompts are often too verbose and can include details that will confuse Floot.

Write it yourself! Use the tricks above to write a good prompt. You can use AI to help you brainstorm or research, but avoid copy and pasting exactly what the AI tells you.

Alternatively, enable Discuss mode and hash out the details with Floot directly. Floot knows more about its own capabilities and your project than ChatGPT or another AI.