Browse all prompting guides The difference matters. Recipe prompts are about describing what to test. Task prompts are about describing what to do. The more precisely you write a task prompt, the more consistently Mahoraga executes it.
Start with shared fundamentals
Apply the shared fundamentals from Overview first: name exact UI targets, define expected outcomes, handle interruptions, and keep scope focused.The structure that works
Every good task prompt follows the same shape:Examples
Simple verification:Execution-specific guidance
1. Use credentials from Apps
If credentials are configured in Apps → Credentials, reference them by name instead of hardcoding login details:2. Be explicit about navigation
Do not assume Mahoraga knows the fastest path between screens. Describe the navigation steps if the route matters for the test:Using test data with /slug
If the same task needs to run with different inputs — different user accounts, different search terms, different product selections — use Test Data instead of writing separate tasks. Type/ in the task prompt input. A dropdown appears listing available datasets with their slugs and sizes. Select one and the slug is inserted at the cursor.
When the task runs, Mahoraga executes it once per row in the dataset automatically.
Example:
/login-credentials has five rows, the task runs five times — once per set of credentials.
→ Test Data
For failure patterns and corrective rewrites, see Troubleshooting Prompts.
When to use tasks vs. Test Studio
Tasks are ephemeral — run once, read the report, move on. If you find yourself running the same task repeatedly, save it as a test case and add it to a suite.
→ Test Cases → Suites