Overview

​

Download the full guide

​

Fundamentals that apply everywhere

1. Be specific about targets. Name screens, buttons, and fields exactly as they appear in UI text.
2. Define expected outcomes. Say what must be true at the end so execution has a clear pass/fail condition.
3. Handle interruptions explicitly. Mention what to do if permissions, onboarding, banners, or popups appear.
4. Keep prompt scope focused. One coherent objective per prompt gives stronger and more reliable results.

​

Choose your workflow

• Prompting for test generation (Recipe / Megumi)
• Prompting for task execution (Tasks / Mahoraga)
• Using test data in prompts (/slug)
• Using backend validations in prompts (@slug)