maestro-mobile-e2e - SKILL.md Agent Skill

name: maestro-mobile-e2e description: Maestro mobile E2E flows for Expo, React Native, iOS, and Android, including mobile smoke tests, auth coverage, Expo dev-client E2E, flaky flow fixes, and verification.

Use Maestro for repeatable mobile user journeys, not unit-level behavior.

Inspect existing Maestro flow locations (.maestro/, maestro/, e2e/, tests/), package scripts, QA docs, app id, fixture data, and current simulator or emulator state.
Keep each flow atomic: one setup path, one route or user journey, one assertion surface.
Extract repeated launch, setup, and login work into shared subflows that match the repo's existing structure.
Put each stable login role or auth state in its own login subflow.
Prefer visible text when it is the user-facing contract; use accessibility ids or testIDs for icons, localized UI, repeated labels, dynamic UI, or stability-sensitive controls.
Verify a representative slice after changing shared flows.
Run the full suite only after the slice passes.

Use the repo's E2E scripts when they exist.
Do not duplicate launch or login blocks across many flows.
Do not chain unrelated screens through fragile back navigation when one-way route checks prove the same contract.
Treat fixture data as part of the E2E contract; document the reset command, roles, records, and identifiers needed to repeat the run.
Keep project-specific app ids, environment names, users, and records in the project QA docs or local flow files, not in this skill.
Check official Maestro docs when syntax, flags, reports, selectors, or flow behavior are uncertain.
Read references/patterns.md when creating or restructuring a Maestro suite.