Athena — roomy-mobile/features/archive/2026-01-05-add-per-screen-maestro-flows/proposal.md

Change: Add Per-Screen Maestro Flows for App Store Screenshot Automation

Why

The current Maestro setup has monolithic flows that navigate through multiple screens sequentially. This prevents agents from launching specific screens with specific data states for targeted screenshot capture. App store submissions require screenshots across 5 device configurations (iPhone 16 Pro Max, iPad Pro 13", Pixel 8, Nexus 7, Pixel Tablet), and agents need programmatic control to capture screenshots for each screen independently.

What Changes

  • Create 21 individual per-screen Maestro flows with parameterized data inputs
  • Reorganize .maestro/ directory structure into screens/, utils/, and orchestration/ subdirectories
  • Add tag-based flow organization for filtering (--includeTags screenshot)
  • Create utility flows for common operations (login, tab navigation)
  • Add missing semantic identifiers to Flutter views for reliable automation
  • Install and configure mobile-mcp for agent-driven screenshot capture
  • Create orchestration flows for full app store screenshot suites per device

Impact

  • Affected specs: New capability maestro-screenshot-automation
  • Affected code:
    • .maestro/ - Complete restructure
    • lib/*/views/*_view.dart - Add semantic identifiers to 9 views
    • instructions/ - Add agent documentation for flow invocation
  • External tools: mobile-mcp MCP server integration

Reacties

Nog geen reacties