About store-screenshots
A skill for producing app-store screenshots from the project's store-screenshots assets. It guides edits to the renderer, capture density, preview review, and restrictions on publishing or committing outputs.
Key features
- 01Direct edits to renderer source
- 02Store-specific capture density guidance
- 03Headline and subline layout constraints
- 04Preview and panel review before reporting
- 05Publishing and commit safeguards
Use cases
- 01Preparing app-store screenshot renders
- 02Reviewing preview and full-size store panels
- 03Avoiding unrequested publication or commits
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ getpaseo/ paseo --skill store-screenshotsAfter installing, type/store-screenshotsin Claude Code to confirm it loaded.
Details
From the project READMEStore screenshots
Follow assets/store-screenshots/README.md. It owns the panels, the creative direction, the render command and the recapture steps. Change copy, crops and layout in assets/store-screenshots/render.mjs, not in the exports.
Working rules:
- Capture at native density:
--pixel-density 3on the iPhone 16 Pro Max,--pixel-density 2on the iPad Pro 13-inch. The default is 1x, which is too soft for the store. - Every headline wraps to two lines and every subline fits on one. The renderer enforces this; rewrite the copy rather than shrink the type.
- Use SF Pro. Never substitute another font.
- Open
output/preview.pngand a full-size panel from each store before you report a render. Show the user the preview. - Do not upload screenshots to a store, a PR, or anywhere public, and do not commit, unless the user asks.
- Stage the demo host on its own port and pick a free Metro port. Do not restart the main daemons.
- When you learn something the next capture needs, fix the README rather than this skill.
Comments
Markdown supported