App Store Screenshot Pack

Start the "App Store Screenshot Pack" loop.

Goal: complete screenshot pack exported at all required store dimensions
Max iterations: 8
Between iterations run: Verify all required store sizes exist in export folder
Exit when: every required dimension has a final exported asset

Step 1: Capture app states, compose marketing frames, and export all required store sizes.

## Before you start

Connect plugins:
- GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs.
- Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes.
- Support tickets (required) — Read customer tickets, feedback, onboarding gaps, and support themes.
- CRM (required) — Read accounts, deals, owners, stages, and onboarding state.
- Linear / Jira (required) — Read roadmap, task, bug, owner, and status context.
- Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals.
- Slack (required) — Post summaries, approvals, blockers, and handoff updates.
- Figma (required) — Inspect designs, dimensions, assets, and handoff notes.

Attach skills:
- Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition.
- Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped.
- CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause.
- Customer operations (optional) — Identify at-risk accounts, missing setup steps, and safe next actions.
- Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial.
- Growth operations (optional) — Evaluate campaign performance, creative tests, CPA, and launch readiness.
- Visual design QA (optional) — Compare implementation against visual expectations and capture regressions.
- Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.