app-store-screenshots
app store screenshots
What it does
- Connected live preview at the canvas's true resolution (scaled to fit)
- Drag-to-reorder screens, inline text editing, layout switcher per screen
- Cross-screen mockups: phone/device frames, captions, and layered elements can be moved across adjacent screens, then exported as clipped crops
- Drop-target screenshot picker (file → saved to public/screenshots/uploaded/<hash>.png)
- Auto-save to app-store-screenshots.json at the project root (git-trackable) + localStorage mirror
- Easy iOS ↔ Android platform switch — separate slide decks live side by side
- One-click bulk PNG export at every Apple/Google-required resolution via html-to-image
Requirements & configuration
- 6. Keep screenshots pointed at existing files. Do not rename screenshot files unless the old project already depended on numeric names and the migration needs them. Existing static paths are fine.
- const fs = require("fs");
- const path = require("path");
- Inside the editor the user will write headlines themselves, but they often need guidance. Apply these rules when reviewing their copy or generating suggestions.
- Re-check line breaks per locale; German/French/Portuguese often need shorter claims.
Configuration: SKILLEXPORT_SIZESPHONE_SCREENSTAMPBACKUP_DIRPRESERVE_DIRTHEMES
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
app-store-screenshots FAQ
What does the app-store-screenshots skill do?
Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS and/or Android apps, or scaffolding a screenshot editor with Next.js. Triggers on app store, play store, screenshots, marketing assets, html-to-image, phone mockup, android screenshots, feature graphic. Connected live preview at the canvas's true resolution (scaled to fit) Drag-to-reorder screens, inline text editing, layout switcher per screen
What does app-store-screenshots require?
6. Keep screenshots pointed at existing files. Do not rename screenshot files unless the old project already depended on numeric names and the migration needs them. Existing static paths are fine. const fs = require("fs"); const path = require("path"); Inside the editor the user will write headlines themselves, but they often need guidance. Apply these rules when reviewing their copy or generating suggestions. Re-check line breaks per locale; German/French/Portuguese often need shorter claims. Configuration keys: SKILL, EXPORT_SIZES, PHONE_SCREEN, STAMP, BACKUP_DIR, PRESERVE_DIR, THEMES.
How do I install app-store-screenshots?
Run: npx -y skills add https://github.com/parthjadhav/app-store-screenshots --skill app-store-screenshots --agent claude-code — the source lives at github.com/parthjadhav/app-store-screenshots.
Maintain app-store-screenshots?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/parthjadhav-app-store-screenshots-app-store-screenshots?ref=badge) npx agentictools info skills/parthjadhav-app-store-screenshots-app-store-screenshots The second line is the CLI lookup for this page — handy in READMEs and docs.
