App Store Screenshot Studio

SkillWeb & browsing

App Store marketing screenshot creation and revision to translate, scrape, crop, and validate `.appstore-screenshots` workspaces. Excludes general image generation.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the App Store Screenshot Studio skill

What this skill tells your AI

The instructions your AI receives, as published by xopoko/build-swift-apps in skills/appstore-screenshot-studio/SKILL.md and read by ahel’s review.

Before invoking Apple-only binaries, confirm the execution context is macOS. From Windows or Linux, run those steps in a Mac SSH project or through an already configured remote transport; do not retry missing Apple binaries locally.

Build App Store screenshots from product reality: inspect the app, choose install promises, write concise panel copy, assemble visuals, crop panels, and prepare App Store Connect assets.

Pair simulator capture/upload work with appstore-screenshot-pipeline, appstore-screenshot-validator, and appstore-review-readiness.

Workflow

  1. Resolve context: repo, README, onboarding, paywall, root screens, existing screenshots/listings, and brand rules. If given an App Store URL, run scripts/scrape.mjs and save JSON under .appstore-screenshots/scraped/. Ask only for missing facts that change direction: app name, devices, locales, panel count.

  2. Initialize:

    node <skill-dir>/scripts/scaffold.mjs --output-dir .appstore-screenshots
    

    Work from .appstore-screenshots/config.json; keep composites in .appstore-screenshots/composites/ and final panels in .appstore-screenshots/panels/.

  3. Plan 3-5 install-focused benefits. Put the clearest value in panel 1. Keep captions readable in search results, concrete, truthful, localizable, and useful as standalone panels.

  4. Generate or assemble visuals. Use real app screenshots when accuracy matters; use image generation only for marketing composites. Keep important text/device edges crop-safe. Do not fake store badges, download buttons, nonexistent features, or misleading UI.

  5. Crop:

    node <skill-dir>/scripts/crop.mjs \
      --input .appstore-screenshots/composites/iphone-en.png \
      --device iphone \
      --output-dir .appstore-screenshots/panels/iphone/en
    
  6. Validate dimensions, file count, and small thumbnails. For ASC upload, use appstore-screenshot-pipeline or asc screenshots validate/upload after IDs/localizations are known.

Workspace

  • .appstore-screenshots/config.json: app, App Store URL, devices, locales, panel count, colors, benefits.
  • .appstore-screenshots/manifest.json: generated/cropped inventory.
  • .appstore-screenshots/scraped/: optional public App Store metadata.
  • .appstore-screenshots/composites/: source composites.
  • .appstore-screenshots/panels/: upload-ready panels.

Presets

DeviceCompositePanelKey
iPhone3456x24001290x2796iphone
iPad6144x27322048x2732ipad

The crop helper treats a composite as three horizontal panels. For other layouts, crop manually with sharp, sips, or the app's asset pipeline.

Quality Bar

Use real product language, high-contrast short headlines, truthful UI, meaning-based localization, and repeated crop/size validation. Do not upload until the user approves final panels or explicitly asks for automated upload.

Signals

GitHub stars
45
Forks
4
Last commit
Aug 2026

ahel review

  • K6low
    bundled executables the agent is told to run

Automated review, not a security audit. Ruleset v1+k2.

Advanced
Catalog kind
skill
Gateway key
appstore-screenshot-studio
Source
github.com/xopoko/build-swift-apps