Define Objectives Clearly
On this page
Goal Clarity Determines the Outcome
An effective prompt for grok-build-0.1 isn’t just about saying what to do—it describes what you want to achieve. The difference is subtle but fundamental: the “what” leaves the model guessing about your expectations, while the “expected result” gives it a precise target.
The Trap of Vague Objectives
Take this example:
“Create a food tracker”
The model has to guess: what kind of interface? Which features? What level of detail for tracking? Which technology? It will produce something, but it will be its vision of the project, not yours.
Now, with a clear objective:
“Create a food tracker that shows the daily calorie breakdown by nutrient when I enter a food. I want a general overview and high-level trends.”
The model knows exactly what you expect: food input, calorie calculation, nutrient breakdown, daily view, and trends. It can produce a relevant result from the first iteration.
Techniques for Formulating Clear Objectives
Describe the Final Result
Instead of describing the action (“add a feature”), describe what the user will see or what the code will do:
- Vague: “Add pagination”
- Clear: “When the list exceeds 20 items, display Previous/Next buttons at the bottom. The current page must be highlighted. The URL must reflect the active page with ?page=N”
Specify Constraints
Constraints eliminate ambiguity:
- “Without adding new dependencies”
- “Maintaining backward compatibility with API v1”
- “Response time must stay under 200ms”
- “Compatible with Node.js 18+“
Provide Input/Output Examples
When working on data transformation or a utility function, an example is worth a thousand words:
“Create a function that transforms a slug into a title. Example: ‘my-blog-post’ → ‘My Blog Post’. Connecting words (of, the, a) are not capitalized unless in the first position.”
Specify What You Don’t Want
Sometimes, saying what you don’t want is as useful as saying what you do want:
“Refactor the component to use hooks, but don’t change the public interface (the props). Existing tests must continue to pass without modification.”
Structure Complex Objectives
For requests that involve multiple changes, structure your objectives in steps or points:
“I want to modernize the authentication system:
- Replace cookie sessions with JWTs
- Add a refresh token with rotation
- Keep the /logout route functional
- Tokens expire after 15 minutes”
Each point is a measurable objective the model can verify.
Key Takeaways
- Describe the expected result, not just the action to take
- Add constraints to eliminate ambiguity
- Provide input/output examples when relevant
- List what you don’t want to modify
- Structure complex objectives in numbered points