Use a skill to scaffold a Next.js editor for store screenshots

Who it is for

If you need marketing screenshots for the App Store or Google Play and want an agent to set up a ready-to-use Next.js editor—instead of starting from a blank page—this skill fits. Official usage: after install, ask a coding agent for store screenshots directly.

The first time, know the side effects. Scaffolding creates Next.js project files; each deck also writes app-store-screenshots.json so git can track it and you can continue later. If you cannot accept these extra files in the repository, do not ask for screenshots yet.

Officially it can be used with Claude Code, Cursor, Windsurf, OpenCode, Codex, and other agents that skills supports. Do not write this roster as exclusive support.

First try in 3 minutes

Use only this official install command:

npx skills add ParthJadhav/app-store-screenshots

Prerequisite: you are already in a project a coding agent may edit, and the goal is App Store / Google Play marketing screenshots. Do not invent a second install path.

Install writes skill files. Before you run it, confirm the current directory is the project you want to use. After the command, do a check that does not scaffold: have the agent confirm the skill is visible and repeat that it will build a Next.js editor and save the deck to app-store-screenshots.json. That is the install-success signal.

Actually saying “I want store screenshots” will generate the editor and the JSON. Have it name the files it will create and whether it will change existing code; allow scaffolding only after you confirm. Success signal: a Next.js editor aimed at store screenshots appears, and you can see app-store-screenshots.json written or updated. The public material does not give a dev command to start the editor; do not invent one.

Usage examples

Example 1: Ask for a set of store screenshots for an app. After install, make that request and let it scaffold the Next.js editor. Confirm the file set first, then allow the write. This page does not set screenshot sizes or device models; the notes only cover “build an editor for the App Store and Google Play”.

Example 2: Continue an existing deck. Officially each deck is saved to app-store-screenshots.json; the project can be tracked by git and resumed. First confirm that JSON is already in the repository, then have the agent continue from it instead of scaffolding a second copy. The public material does not write the JSON fields; do not invent an upload directory.

Limits

This is a marketing-screenshot editor skill, not an app-submission tool, and not a publisher that uploads to the App Store console on its own. Do not invent a size table or store APIs.

Install is only npx skills add ParthJadhav/app-store-screenshots. Do not write Claude Code, Cursor, Windsurf, OpenCode, Codex as the only usable range. Do not treat the skills GitHub address as a second install source.

Scaffolding and writing JSON both change the repository and must be confirmed first. The public material has no uninstall steps and no development-server command.

Repository address:

https://github.com/parthjadhav/app-store-screenshots