Overview
The quality of your prompts directly impacts Nova Act’s reliability and success rate. Nova Act works most reliably when tasks can be accomplished in fewer than 30 steps. This guide covers best practices for writing effective prompts.Core Principles
1. Be Direct and Succinct
Tell the agent exactly what to do, not what you want to achieve. Avoid conversational or exploratory language.- Don't
- Do
- Don't
- Do
2. Provide Complete Instructions
Specify all the details the agent needs to make decisions. Don’t leave choices or values ambiguous.- Don't
- Do
3. Break Up Large Tasks
Split complex multi-step workflows into smaller, focusedact() calls. This improves reliability and makes debugging easier.
- Don't
- Do
Further Breaking Down Tasks
If the agent still struggles, break it down even more:Writing Effective Prompts
Specify Actions Clearly
Include Contextual Hints
If Nova Act struggles with specific UI elements or navigation, add hints:Use Variables for Dynamic Data
Date Handling
Specify dates in absolute time format:Handling Extraction
When you need information back from the page, be explicit about what you want:Common Patterns
Search and Filter
Form Filling
Navigation with Validation
Handling Common Challenges
Obstacle Navigation
Search Initiation
If the search button is hard to find:Multi-Step Forms
Break forms into stages:Testing and Iteration
When developing prompts:- Start simple: Begin with basic prompts and add detail as needed
- Observe failures: When
act()goes off track, enhance the prompt with hints - Break it down: If reliability is inconsistent, split into smaller steps
- Add constraints: Specify stopping conditions and what to avoid
Example: Iterative Refinement
Best Practices Summary
- Be direct - Use imperative commands, not conversational language
- Be complete - Include all necessary details and constraints
- Break it up - Split complex tasks into focused
act()calls under 30 steps each - Add hints - Guide the agent with contextual information when needed
- Use absolute values - Especially for dates and quantities
- Specify returns - Clearly state what information you want back with
act_get() - Iterate - Refine prompts based on observed behavior