Vaulter

Building with AI

Getting better results

Four habits that make the agent faster and more accurate: fresh chats, visual context, outcome-first requests, and knowing where AI struggles.

The agent is capable, but how you talk to it makes a real difference. These habits will get you faster, more accurate results.

1. Start a fresh chat for a new task

The agent works best with focused context. When you move on to something unrelated, start a new chat. A long thread that has drifted across many different topics is harder for the agent to reason about than a clean one aimed at a single goal.

2. Show, do not just tell

Words only go so far. When something looks wrong, show it:

  • Attach a screenshot to your message. You can attach up to 4 images or documents per message, 8 MB each, and this is the single highest-leverage habit on this page.
  • Point at the element with Edit Mode if the change is visual, and skip the agent entirely.
  • Name the page and describe exactly where on it the problem is.

The agent fixes what it can see far more reliably than what it has to guess at.

3. Ask by outcome, not by implementation

Describe the result you want, not how you think it should be built. "Users should be able to reset their password from the login page" is better than a step-by-step guess at the code. The agent is good at figuring out the how once it understands the what.

4. One thing at a time

A focused request lands more reliably than five unrelated changes packed into one message. Send the first change, watch it land, send the next. The loop is fast enough that small steps beat big batches.

5. Plan the big things before building them

For a large feature, use Plan mode first. The agent will read your project, ask you clarifying questions, and produce a written plan with the goal, scope, and open questions resolved, without touching your app. Then switch to Build and point at the plan. Ambitious features go much better when the thinking happens before the building. Plan mode is a paid feature.

6. Expect a few misses, and correct quickly

AI is not human. It is a statistical model, and it will always make some mistakes. That is not a sign anything is broken. When a change is not right, tell the agent what is off and it will adjust. Short, specific feedback beats a long re-explanation, and auto-fix already catches a whole class of problems before they reach you.

None of these are rules. They are the difference between fighting the agent and working with it. Once they become habits, building gets noticeably smoother.