app-store-screenshots
Generate App Store and Google Play marketing screenshots using Next.js. Use when the user wants to create app store screenshots, marketing screenshots, or device mockup exports for iOS, iPad, or Android.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- app-store-screenshots
- metadata
- { "author": "ParthJadhav" }
- description
- Generate App Store and Google Play marketing screenshots using Next.js. Use when the user wants to create app store screenshots, marketing screenshots, or device mockup exports for iOS, iPad, or Android.
03 SKILL.md 正文
App Store & Google Play Screenshots Generator
Build a Next.js application for creating exportable App Store and Google Play marketing screenshots across multiple device types and platforms.
Core Philosophy
"Screenshots are advertisements, not documentation. Every screenshot sells one idea."
Key Capabilities
Supports rendering screenshots for:
- iPhone (portrait with mockup.png frame)
- iPad (portrait, CSS-rendered frame)
- Android Phone (portrait, CSS-rendered)
- Android Tablets (7" and 10", portrait + landscape)
- Google Play Feature Graphic (1024×500 banner)
Core Workflow
Before coding, gather these inputs:
- Screenshot image locations
- App icon PNG path
- Brand colors (accent, text, background)
- Typography selection
- Feature prioritization
- Desired slide count
- Visual style direction
- Target platform(s)
- Language localization needs
- Theme customization preferences
Technical Foundation
Uses html-to-image for export, not html2canvas, due to superior CSS handling.
Critical implementation patterns:
- Pre-load images as base64 data URIs to prevent non-deterministic fetch failures
- Double-call export technique (first warm-up, second production)
- Device-agnostic width formulas that scale proportionally across canvas sizes
- Slide factory pattern for reusable device-specific templates
Canvas Dimensions
Design at largest resolution per category; exports scale down automatically:
| Device | Dimensions |
|---|---|
| iPhone | 1320×2868px |
| iPad | 2064×2752px |
| Android phone | 1080×1920px |
| Android tablets (portrait) | 1200×1920 and 1600×2560 |
| Android tablets (landscape) | 1920×1200 and 2560×1600 |
| Google Play Feature Graphic | 1024×500px |
Layout Patterns
- Portrait phones: device centered, slightly lower than canvas center
- Landscape tablets: caption occupies left 34%, device on right with negative space
- Visual variation: layouts differ between adjacent slides to avoid templated feel
Architecture
The entire generator lives in a single page.tsx with:
- Canvas dimensions matching the largest required resolution per device
- Width formula functions that scale device frames proportionally
- Device components using CSS frames (Android, iPad) or PNG mockups (iPhone)
- Slide factories accepting a device component and returning reusable slide definitions
- Pre-loaded image cache converting all assets to base64 data URIs
Export Strategy
// Double-call pattern — first primes fonts/images, second produces clean output
async function exportSlide(element: HTMLElement): Promise<string> {
await toPng(element); // warm-up call
return toPng(element); // production call
}
This prevents blank or transparent regions common in single-pass exports.
Additional Features
- Localization with RTL text direction support
- Theme presets
- Bulk export with numbered filenames for correct sorting
Implementation Notes
- Never use
html2canvas— usehtml-to-imageinstead - Pre-convert all images (screenshots, icon) to base64 before rendering
- Landscape tablet slides exclusively use caption-left + device-right composition
- Avoid repeated layouts on adjacent slides
04 同仓库更多 Skills
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.