Prompting best practices for native.builder

In the Builder factory, prompts are your briefs to the agents on the line. A clear brief means less rework, fewer credits spent, and software shipped faster. These practices help you get production-quality output on the first pass — whether you’re a solo builder or running vibe coding for enterprise with a shared team. Agencies using Builder as an AI prototyping platform for client delivery should brief agents the way you’d brief a dev team: scope, audience, and must-haves up front.

​

Start with a clear goal

Before prompting, know what you want:

• What — The type of app (dashboard, landing page, tool)
• Who — Who will use it
• Key features — The 2–3 things it must do in v1

​

Be specific

Vague prompts produce vague results. Compare:

​

Build incrementally

Don’t try to build everything in one prompt. Break work into steps:

​

Assign the right agent

Each agent is a specialist on your factory floor — use the right one for the stage you’re in: Switch agents from the agent picker in the chat panel. Starting with Product Architect saves credits by preventing expensive rebuilds.

​

Reference what exists

When iterating on an existing project, point to specific parts:

• “Update the Settings page to add a dark mode toggle”
• “Change the primary button color on the landing page to purple”
• “Add a new route at /analytics with a bar chart of monthly revenue”

The AI has context about your project’s current code and structure.

​

Use real content

Replace placeholder text with realistic content early:

• Use actual product names, not “Lorem ipsum”
• Provide sample data that matches your use case
• Include real error messages and edge cases you expect

This helps the AI make better structural decisions.

​

Enhance your prompt

Use the Enhance prompt button in the chat composer to expand a short idea into a detailed prompt before sending. This is especially useful when you know what you want but aren’t sure how to phrase it.

​

When something goes wrong

If the AI produces unexpected results:

1. Be specific about the problem — “The sidebar overlaps the content on mobile” not “it looks broken”
2. Ask for one fix at a time — Don’t combine unrelated changes
3. Revert if needed — Use the Versions panel to roll back to a working snapshot (paid plans)
4. Rephrase — Sometimes rewording the request produces a better result

​

Model selection

Different models have different strengths and credit costs. Builder is a model-agnostic AI app builder — switch models without migrating your project:

• Standard models — Fast, cost-effective, good for most tasks
• Premium models — Better reasoning for complex features (Pro plan and above)

Choose models from the model picker in the chat panel. Premium models consume more credits per message.

​

Attach images and files

• Paste images — Paste a PNG or JPEG into the composer with ⌘V / Ctrl+V. It appears as an attachment chip before you send.
• Multi-file upload — Select several files at once when attaching to a message.
• Cloud files — Connect Google Drive or Dropbox and use those files as sources without re-uploading.

Keep attachments relevant. Extra noise makes it harder for Builder to focus on what matters.

​

Stay oriented in long chats

Builder recalls important earlier decisions in long threads and can carry key project facts across sessions. You still get better results when you:

• Restate the current goal when you change direction
• Point at the file, route, or screen you mean
• Answer multiple-choice questions when the agent asks — tap an option instead of typing a paragraph when you can

​

Edit what you already sent

You can copy, edit, or resend your own messages. Use edit + resend when a prompt was almost right instead of stacking a correction underneath.