Prompting effectively
Give the agent a clear outcome, context and acceptance checks
A useful request explains the result you want and how you will know it works.
Describe the outcome
Add a customers table to the dashboard with name, email and signup
date. Let me search by name and sort by signup date. Keep the current
colors and layout. Confirm that search and sorting work together.
Include who uses the feature, the data it needs and any constraints. You can specify technical requirements when they matter; otherwise start with the behavior.
Give enough context
- Name an existing page, file or workflow that should change.
- Connect services when the task needs access to them.
- State standing preferences and decisions you want preserved.
- For a bug, give the action, expected result and actual result, including the exact error if available.
Work in reviewable stages
For a new product, describe the overall shape first. Then ask for focused stages you can review. For a large task, state the milestones and let Ameca organize the work and any delegation. You do not need to assign fixed specialist roles.
Review the change and the reported checks before moving on. If something is wrong, name the specific behavior instead of asking for an unexplained full rewrite.
State boundaries
Say what should stay the same, which accounts or environments may be used, and when you want to review a consequential step. Give secrets through the appropriate configuration controls, not the prompt.
For longer work, see Agents and goals. For allowances and request cost, see Limits and usage.