メニュー
Create, revise, translate, scrape, crop, validate, and prepare App Store marketing screenshots and `.appstore-screenshots` workspaces. Not for general image generation.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Search Apple Dev Search for Swift, SwiftUI, Xcode, iOS, macOS, and Apple-platform community articles, tutorials, blogs, and write-ups.
Apple firmware and binary reverse engineering with the `ipsw` CLI: IPSW/kernelcache download/extraction, dyld_shared_cache disassembly, private headers, entitlements, Mach-O analysis, Apple internals, KEXTs, and security research.
Use when App Store listing text must be translated or market-adapted across locales, including descriptions, keywords, What's New, subtitles, names, privacy text, and App Store Connect languages. Not for non-translation metadata edits, release-note drafting, or subscription/IAP display-name localization.
Use when App Store listing metadata in canonical `./metadata` JSON needs field edits, validation, push, keyword sync, or legacy fastlane migration. Not for translation-first localization, release-note drafting, or subscription/IAP display-name localizations.
Use for the concrete macOS Developer ID notarization command path with xcodebuild export plus `asc notarization` submit, status, log, and stapling. Not for broad packaging readiness review or signing-only diagnosis.
Set territory-specific subscription and IAP pricing with `asc` setup, pricing summary, CSV import, price-point, availability, and schedule commands. Use for PPP or localized pricing strategies.
| name | appstore-screenshot-studio |
| description | Create, revise, translate, scrape, crop, validate, and prepare App Store marketing screenshots and `.appstore-screenshots` workspaces. Not for general image generation. |
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.
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.
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/.
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.
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.
Crop:
node <skill-dir>/scripts/crop.mjs \
--input .appstore-screenshots/composites/iphone-en.png \
--device iphone \
--output-dir .appstore-screenshots/panels/iphone/en
Validate dimensions, file count, and small thumbnails. For ASC upload, use appstore-screenshot-pipeline or asc screenshots validate/upload after IDs/localizations are known.
.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.| Device | Composite | Panel | Key |
|---|---|---|---|
| iPhone | 3456x2400 | 1284x2778 | iphone |
| iPad | 6144x2732 | 2048x2732 | ipad |
The crop helper treats a composite as three horizontal panels. For other layouts, crop manually with sharp, sips, or the app's asset pipeline.
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.