Describing what the app should do

Functionality comes from the prompt

There is no settings form for features. What the app does is whatever you describe in the chat. Want a pricing table, a contact form, a countdown, or a gallery? Ask for it in plain words. The clearer the request, the closer the first build lands.

The slash tool menu

Type a slash in the chat to open the tool options panel. It lists the modes the builder can work in, grouped as Plan, Explore, Build, Review, Ship, and Integrate. Each one scopes what the builder does on a given turn. You can ask it to plan an approach before writing any code, explore the files it has already made, run a build, or review what it produced. Choosing the right mode keeps a turn focused instead of letting it try to do everything at once.

Plan before you build

For anything past a single page, ask for a plan first. It is like agreeing on the shopping list before anyone drives to the store: fixing the list is cheap, returning a full cart is not. The builder lays out the pieces it intends to create, you correct the plan, and only then does it write code.

Keep requests specific

Change one thing at a time when you can. "Add a FAQ section with four questions below the pricing table" is far easier for the builder to get right than a paragraph of unrelated changes in one message. You are not limited to one request per turn, but tightly scoped turns produce cleaner diffs and are much easier to review.