Plan, Discuss, and Build
Three ways to talk to Floot — think it through first, ask questions, or ship the change.
Not every message should write code. Floot has three modes, and picking the right one is the single easiest way to get better results.
Plan mode
Choose Plan first instead of Build when you start a new project and you want to think before you ship. Floot interviews you about the app — who it is for, what the core flows are, what can wait for version two — and then writes a plan into your project.
The plan appears on the right as it is written. You can keep chatting to refine it: add a feature, cut a screen, change the data model. Nothing is built yet.
When you are happy, click Build Plan. Floot switches into build mode and uses the plan as the blueprint for the initial build.
Vague prompts route here automatically
If you start with something broad like "build me a game", Floot may take you to planning on its own — a two-minute conversation up front saves a lot of rework.
Discuss mode
Toggle Discuss in the chat pane to ask questions without changing anything. Use it to:
- Understand how something in your app currently works
- Weigh two approaches before committing to one
- Work out why a feature behaves the way it does
- Sanity-check an idea that might be a big change
Floot knows your project and its own capabilities far better than a general-purpose chatbot does. When you have settled on an approach, turn Discuss off and ask for the change.
Build mode
The default. Describe one change and Floot makes it. Keep each prompt to a single feature, change, or fix so you can verify it before moving on — see Prompting tips.
A rhythm that works
Plan the app → build one feature → test it in the preview → build the next. Handle visual polish last, using the Annotate tool.