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.Documentation Index
Fetch the complete documentation index at: https://docs-builder.nativelyai.com/llms.txt
Use this file to discover all available pages before exploring further.
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
New projects start with the Product Architect agent, which helps you define scope before code is written. Use it to plan, then switch to the Builder agent to implement.
Be specific
Vague prompts produce vague results. Compare:| Weak | Strong |
|---|---|
| ”Make a dashboard" | "Build a sales dashboard with a revenue chart, a table of recent orders, and filters for date range and region" |
| "Fix the styling" | "Make the header sticky, increase button padding to 12px, and use a dark background (#111) with white text" |
| "Add auth" | "Add email/password login with a sign-in page, sign-up page, and redirect to /dashboard after login” |
Build incrementally
Don’t try to build everything in one prompt. Break work into steps:Layout and navigation
“Create the main layout with a sidebar, header, and content area. Add navigation links for Dashboard, Settings, and Profile.”
Core feature
“Add a task list to the Dashboard page. Each task has a title, status badge, and a checkbox to mark complete.”
Assign the right agent
Each agent is a specialist on your factory floor — use the right one for the stage you’re in:| Agent | Factory role |
|---|---|
| Product Architect | Planning stage — PRDs, architecture, scoping before code |
| Builder agent | Production stage — writes code, implements features, fixes bugs |
| Task Planner | Operations — breaks work into tasks, manages the task board |
| Feedback | Quality loop — captures bugs, requests, and product signal |
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
/analyticswith a bar chart of monthly revenue”
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
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:- Be specific about the problem — “The sidebar overlaps the content on mobile” not “it looks broken”
- Ask for one fix at a time — Don’t combine unrelated changes
- Revert if needed — Use the Versions panel to roll back to a working snapshot (paid plans)
- Rephrase — Sometimes rewording the request produces a better result
Model selection
Different models have different strengths and credit costs:- Standard models — Fast, cost-effective, good for most tasks
- Premium models — Better reasoning for complex features (Pro plan and above)
Next steps
Getting started
Apply these tips to your first project.
Plans & credits
Understand model access and credit costs.