Build, Plan and Discuss
Three modes, and picking the right one for what you are asking.
The composer has three modes. Using the wrong one is the most common reason Studio feels either too eager or too slow.
| Mode | What it does | Use it when |
|---|---|---|
| Build | Writes and runs code now | You know what you want and want it built |
| Plan | Produces an approach without changing files | The work is big, or you are unsure of the shape |
| Discuss | Talks, changes nothing | You are asking a question about the codebase |
The habit worth forming
For anything larger than a small change, Plan first. Read the plan, correct it, then switch to Build. A plan is cheap to change; a wrong implementation is not.
For "why does this file do X" — use Discuss. Build mode will answer, but it may also decide to helpfully change something.
You're done when the mode matches your intent before you press send.
Gotchas
- Build mode edits files. That is the point, and it surprises people who meant to ask a question.
- Plan does not carry over automatically. Approve or restate it when you switch to Build.