What problem does it solve? Setting up end-to-end testing for an Expo app requires coordinating many moving parts — a dedicated Supabase project, environment variables, database migrations, a test account, a native dev-client build, and Maestro flows — and skipping any step causes silent failures that only surface mid-run. This Skill walks through the full one-time setup with a verifiable proof for every step, so the environment is confirmed working before any autopilot run or E2E suite executes. ## Core Features & Use Cases - Guided environment provisioning: Creates .env.e2e with placeholders, verifies gitignore coverage, applies migrations via supabase db push, and installs a database marker table that prevents seeds from ever running against dev or prod. - Test account and dev-client setup: Creates the test user through the Supabase Admin API with confirmed email, verifies login with the anon key, and rebuilds the Expo dev-client with correct ad-hoc signing so native modules and secure storage work. - Canary verification: Ends with a Maestro canary flow that must log in and reach a screen behind auth, proving the whole chain works before real test flows run. - Use Case: Before running an autonomous implementation workflow whose plan contains [E2E] checkboxes, run this setup once so the E2E gate passes instead of halting the run. ## Quick Start Ask the assistant to set up the E2E testing environment with Maestro and a dedicated Supabase project for this Expo app, then follow the step-by-step proofs it produces.
