play-store-screenshots

Automate Google Play Store screenshot and graphic generation with Puppeteer.

58|4|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/po4yka/RIPDPI --skill play-store-screenshots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: play-store-screenshots
Source: https://github.com/po4yka/RIPDPI/tree/main/.claude/skills/play-store-screenshots
Command: npx skills add https://github.com/po4yka/RIPDPI --skill play-store-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating Google Play Store assets such as phone screenshots, feature graphics, and marketing visuals for RIPDPI is time-consuming and prone to inconsistency; this skill streamlines the process to ensure branding alignment and Play Store compliance.

Core Features & Use Cases

  • Generate 1080x1920 phone screenshots, 1024x500 feature graphics, tablet screenshots, and marketing images for RIPDPI.
  • Update and refresh assets in play-store-screenshots/src/app/page.tsx and public/screenshots/ via automated captures (Puppeteer batch) to keep listings up to date.
  • Align assets with DESIGN.md tokens and Play Store guidelines (max 8 screenshots per device type, 24-bit PNG, text overlays under 20%, no promotional text).

Quick Start

Use the generator to capture and publish Play Store assets for RIPDPI using the provided scripts.

Frequently Asked Questions about play-store-screenshots

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Google Play Store screenshot generation?

Automate Google Play Store screenshot generation by running Puppeteer batch captures to produce phone screenshots, tablet visuals, and feature graphics, directly updating repository assets for repeatable exports.

What are the Google Play Store asset requirements for screenshots and feature graphics?

Google Play Store asset requirements mandate 24-bit PNG format without alpha, a maximum of 8 screenshots per device type, and text overlays covering under 20% of the image.

How do I capture phone and tablet screenshots in a production build workflow?

Capture phone and tablet screenshots in a production build workflow using Puppeteer batch capture, generating 1080x1920 phone visuals and tablet graphics to refresh app listings.

Can I use Puppeteer to batch capture marketing visuals for the Play Store?

Yes, you can use Puppeteer to batch capture marketing visuals for the Play Store, automating the creation of 1024x500 feature graphics and phone screenshots for repository integration.

Does this approach keep Play Store assets aligned with branding tokens?

Yes, this approach aligns generated Play Store assets with DESIGN.md branding tokens, ensuring visual consistency across phone screenshots, tablet visuals, and feature graphics.

What is the best way to update Play Store screenshots in a repository?

The best way to update Play Store screenshots in a repository is automating captures that refresh files in src/app/page.tsx and public/screenshots/, ensuring assets meet store guidelines.