What problem does it solve? Coordinating a live Tauri dev instance (Vite on port 5174, MCP bridge on 9223) for automated end-to-end testing is error-prone: orphaned processes hold ports, the SQLite database accumulates stale state, and agents cannot set environment variables or delete files outside their sandbox. This Skill provides sanctioned PowerShell scripts and a rigorous DOM-plus-screenshot testing methodology so QA agents can reliably start, reset, diagnose, and verify the app. ## Core Features & Use Cases - Lifecycle management: Single dev-env.ps1 script handles Up, Down, Status, Restart, Logs, and baseline serving at a specific commit (-At), with port-based state detection and env-var injection for gated app seams. - Environment reset and hygiene: clean-fredo-db.ps1 wipes the live SQLite DB for fresh-slate tests, and process-hygiene.ps1 lists or kills orphaned opencode/node processes that block new runs. - E2E testing methodology: Nine DOM test patterns, mandatory dual DOM-plus-screenshot verification per acceptance criterion, a regression smoke checklist, and diagnostics for known failure signatures (wedged MCP bridge, stale driver session). - Use Case: A QA agent dispatched against spec branch spec/2762 runs dev-env.ps1 -Action Up -Spec 2762, connects via tauri_driver_session start, tests each user-observable acceptance criterion with screenshots, and reports a structured pass/fail table. ## Quick Start Start the dev instance by running the dev-env script with Action Up, then connect with tauri_driver_session start and begin testing acceptance criteria with paired DOM snapshots and screenshots.