Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From Build Swift Apps
Creates, revises, translates, crops, validates, and prepares App Store marketing screenshots via a workspace workflow. Useful for building `.appstore-screenshots` assets from app inspection and install-promise copy.
npx claudepluginhub xopoko/build-swift-apps --plugin build-swift-appsHow this skill is triggered — by the user, by Claude, or both
Slash command
/build-swift-apps:appstore-screenshot-studioThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
Generates 5–6 App Store screenshots from a brand spec, product screenshots, or a live App Store listing via Pika MCP. Outputs story-driven 1290×2796 PNGs ready for App Store Connect.
Generates App Store/Google Play promotional screenshots in Pencil (.pen) format using 5-agent team for strategy, Pencil design, copywriting, spec validation, and quality review. Use for app promo images.
Provides App Store Optimization strategy for search visibility and conversion, including keyword research, App Store description writing, screenshot placement, Custom Product Pages, and in-app review prompts.
Share bugs, ideas, or general feedback.
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.