shots

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Shots

Generate high-converting App Store screenshots. The job is not to decorate existing screens. The job is to infer the app's market, visual language, and strongest promise, then turn that into crop-safe screenshot panels built to drive installs.

生成高转化率的App Store截图。此工具的核心并非装饰现有界面，而是推断应用的目标市场、视觉语言及核心价值主张，进而制作出符合裁剪要求、能有效提升安装量的截图面板。

Why Screenshot Quality Matters

截图质量的重要性

Research shows optimized app store screenshots can achieve:

68.2% conversion rate vs 26.4% industry average
720% improvement in install rate
7-second decision window - first 2-3 screenshots are critical

This skill is designed to leverage GPT Image 2's strengths (95%+ text accuracy, UI mockup excellence, 4K output) combined with proven conversion patterns (Story Flow, hybrid captions, visual hierarchy) to create high-converting marketing assets.

研究表明，优化后的应用商店截图可实现：

68.2%的转化率，远超行业平均水平的26.4%
720%的安装率提升
7秒决策窗口——前2-3张截图至关重要

本工具旨在结合GPT Image 2的优势（95%+的文字准确率、出色的UI原型制作能力、4K输出）与经过验证的转化模式（故事流、混合字幕、视觉层级），打造高转化率的营销素材。

Intent Router

意图路由

Intent	Detection	Action
Create new	No existing shot referenced, or "new", "create", "generate", or an App Store URL	Run the Create Questionnaire, then follow reference/create.md
Revise	References a shot ID, or says "revise", "change", "fix", "redo"	Follow reference/revise.md
Translate	Mentions a locale or says "translate", "localize"	Follow reference/translate.md
Scrape only	Says "scrape", "fetch metadata", "import" with a URL	Follow reference/scrape.md
Ambiguous	You cannot tell which flow is intended	Ask the user what they want to do

意图	检测条件	操作
创建新截图	未提及现有截图，或包含“new”“create”“generate”关键词，或提供App Store链接	启动创建问卷，随后遵循reference/create.md流程
修改截图	提及截图ID，或包含“revise”“change”“fix”“redo”关键词	遵循reference/revise.md流程
翻译截图	提及语言区域，或包含“translate”“localize”关键词	遵循reference/translate.md流程
仅爬取数据	包含“scrape”“fetch metadata”“import”关键词并附带链接	遵循reference/scrape.md流程
意图模糊	无法判断用户所需流程	询问用户具体需求

Argument Parsing

参数解析

```
/shots
```
— start the create questionnaire
```
/shots <url>
```
— scrape the listing, then continue with create
```
/shots <description>
```
— create using that context
```
/shots revise [shot-id]
```
— revision flow

/shots translate [shot-id|run-id] [locale]

— localization flow

```
/shots scrape <url>
```
— scrape only

```
/shots
```
—— 启动创建问卷
```
/shots <url>
```
—— 爬取应用列表，随后进入创建流程
```
/shots <description>
```
—— 根据提供的上下文创建截图
```
/shots revise [shot-id]
```
—— 进入修改流程

/shots translate [shot-id|run-id] [locale]

—— 进入本地化流程

```
/shots scrape <url>
```
—— 仅执行爬取操作

Shared Setup

通用设置

Run these checks before every sub-command. Do not skip them.

Run

npm list --prefix {{scripts_path}} sharp 2>/dev/null

. If it fails, run

npm install --prefix {{scripts_path}}

Run

node {{scripts_path}}/scaffold.mjs --init --output-dir .shots/

For create, revise, and translate, verify
```
OPENAI_API_KEY
```
or
```
FAL_KEY
```
is set. Stop immediately if neither exists.
Read
```
.shots/config.json
```
if present.

{{scripts_path}}

is the

scripts/

directory next to this file.

scaffold.mjs --init

is the source of truth for the workspace contract. It creates the default

config.json

and

manifest.json

; agents should fill those files in rather than inventing their own schema.

执行任何子命令前需完成以下检查，请勿跳过：

运行

npm list --prefix {{scripts_path}} sharp 2>/dev/null

。若执行失败，运行

npm install --prefix {{scripts_path}}

。

运行

node {{scripts_path}}/scaffold.mjs --init --output-dir .shots/

。

对于创建、修改和翻译流程，需验证
```
OPENAI_API_KEY
```
或
```
FAL_KEY
```
已配置。若两者均未配置，立即停止操作。
若存在
```
.shots/config.json
```
文件，读取该文件内容。

{{scripts_path}}

指的是本文件所在目录下的

scripts/

文件夹。

scaffold.mjs --init

是工作区约定的基准，它会创建默认的

config.json

和

manifest.json

；Agent应填充这些文件，而非自行创建新的 schema。

Create Questionnaire

创建问卷

When the create flow starts and the config is missing or incomplete, ask for all of these in one message:

App name
App Store URL — ask explicitly: "Do you have an existing App Store or Google Play listing? If so, paste the URL." This is the highest-value input: it unlocks automated metadata scraping, competitor research, and existing screenshot analysis.
Number of screenshots to generate
Devices: iPhone, iPad, Android Phone
Languages/locales

Optional (only ask if the user wants to override what you'll infer):

Visual style override
Brand colors
Differentiator override

Defaults:

```
panelCount
```
:
```
3
```
```
devices
```
:
```
["iphone"]
```
```
locales
```
:
```
["en"]
```
Screenshot counts above 3 are produced as multiple 3-panel composites.

当创建流程启动且配置文件缺失或不完整时，需一次性向用户询问以下所有信息：

应用名称
App Store链接 —— 明确询问：“您是否已有App Store或Google Play应用列表？若有，请粘贴链接。”这是价值最高的输入信息：它可解锁自动元数据爬取、竞品调研及现有截图分析功能。
需生成的截图数量
目标设备：iPhone、iPad、Android Phone
语言/区域

可选信息（仅当用户希望覆盖系统推断结果时询问）：

视觉风格覆盖设置
品牌配色
差异化卖点覆盖设置

默认值：

```
panelCount
```
:
```
3
```
```
devices
```
:
```
["iphone"]
```
```
locales
```
:
```
["en"]
```
超过3张的截图将以多组3面板合成图的形式生成。

Research Contract

调研约定

Before drafting copy or generating images, build and save a

strategyBrief

.shots/config.json

. This is the source of truth for benefits and prompt assembly.

Use sources in this order:

User-provided brand/colors/style overrides
App Store URL and scraped listing data
The local repo: README, onboarding, navigation, models, root screens, existing copy
```
.shots/app-screenshots/
```
```
.shots/inspo/
```
Competitor listings and review language
Ask the user only for the highest-value unknown that cannot be inferred

If an App Store URL exists, do full-stack research by default: listing, screenshots, direct competitors, and review language. If no URL exists, infer from the repo first. If no repo signal exists, infer from screenshots/inspo. If the app is still unclear, ask the user.

Follow reference/strategy.md to:

identify theme, colors, and audience
map the competitor space
extract market-native words and repeated pain language
save the strategy brief
draft 6-8 benefits ranked for install intent

在撰写文案或生成图像前，需在

.shots/config.json

中构建并保存

strategyBrief

（策略简报），这是核心优势及提示词组装的基准。

调研信息来源优先级如下：

用户提供的品牌/配色/风格覆盖设置
App Store链接及爬取的应用列表数据
本地代码库：README、引导流程、导航结构、模型、主界面、现有文案
```
.shots/app-screenshots/
```
```
.shots/inspo/
```
竞品列表及评论语言
仅当无法通过上述途径推断时，才向用户询问最高价值的未知信息

若提供了App Store链接，默认需进行全栈调研：应用列表、截图、直接竞品及评论语言。若未提供链接，则优先从代码库推断。若代码库无相关信号，则从现有截图/参考素材推断。若仍无法明确应用信息，再询问用户。

遵循reference/strategy.md完成以下操作：

确定主题、配色及受众
梳理竞品环境
提取市场通用词汇及反复出现的痛点描述
保存策略简报
草拟6-8条按安装意向排序的核心优势

Prompt Contract

提示词约定

Always build prompts from the saved

strategyBrief

and approved benefits. Follow reference/prompting.md.

Hard rules:

Generate screenshots in batches of 3 panels per composite by default.
Each composite must crop cleanly into standalone portrait screenshots.
At least 2 of every 3 panels should show a device unless the concept clearly benefits from a text-only or lifestyle panel.
Headline text must be short, high-contrast, thumbnail-readable, and verbatim.
Device screens must show concrete UI, not generic placeholder app chrome.
Use visual facts, not vague praise words.
Decorative depth elements must reinforce the feature being sold.
Do not include app store badges, download buttons, or fake platform chrome.

始终基于已保存的

strategyBrief

及已确认的核心优势构建提示词。遵循reference/prompting.md。

硬性规则：

默认以每组3面板合成图的形式生成截图。
每组合成图必须能清晰裁剪为独立的竖版截图。
每3张面板中至少有2张需展示设备界面，除非创意方案明确需要纯文字或生活场景面板。
标题文字必须简短、高对比度、在缩略图尺寸下清晰可读，且需完全符合原文。
设备界面必须展示具体UI，而非通用占位符应用框架。
使用可视化事实，而非模糊的赞美词汇。
装饰性深度元素必须强化所推广的功能。
不得包含应用商店徽章、下载按钮或伪造的平台框架。

Existing Shot Flows

现有截图流程

For revise and translate:

Read
```
.shots/manifest.json
```
and list recent shots if no shot ID was supplied.
Reuse the saved
```
strategyBrief
```
unless the user explicitly changes positioning, audience, or visual direction.
Treat the original prompt as the base artifact and append precise change/preserve instructions.

对于修改和翻译流程：

读取
```
.shots/manifest.json
```
，若未提供截图ID，则列出近期生成的截图。
除非用户明确改变定位、受众或视觉方向，否则复用已保存的
```
strategyBrief
```
。
将原始提示词作为基础工件，并附加精确的修改/保留指令。

Dimensions

尺寸规格

Device	Composite	Final panel	Key
iPhone	`3456x2400`	`1284x2778`	`iphone`
iPad	`6144x2732`	`2048x2732`	`ipad`
Android Phone	`3240x1920`	`1080x1920`	`android`

设备	合成图尺寸	最终面板尺寸	标识
iPhone	`3456x2400`	`1284x2778`	`iphone`
iPad	`6144x2732`	`2048x2732`	`ipad`
Android Phone	`3240x1920`	`1080x1920`	`android`

Config Shape

配置文件结构

The initialized

config.json

contains:

app metadata:

appName

appStoreUrl

devices

locales

panelCount

generation defaults:

generation.provider

generation.quality

generation.timeoutMs

generation.partialImages

brand colors:
```
brandColors
```
App Store data:
```
aso
```
,
```
ratings
```
,
```
scrapedAssets
```
strategy state:
```
strategyBrief
```
copy state:
```
benefits
```

Do not hand-author a fresh schema in the agent instructions. Read the generated file and fill it in.

初始化后的

config.json

包含以下内容：

应用元数据：

appName

、

appStoreUrl

、

devices

、

locales

、

panelCount

生成默认设置：

generation.provider

、

generation.quality

、

generation.timeoutMs

、

generation.partialImages

品牌配色：
```
brandColors
```
App Store数据：
```
aso
```
、
```
ratings
```
、
```
scrapedAssets
```
策略状态：
```
strategyBrief
```
文案状态：
```
benefits
```

请勿在Agent指令中手动创建新的schema，应读取生成的文件并填充内容。

References

参考文档

reference/create.md — end-to-end create flow
reference/strategy.md — research, strategy brief, benefits
reference/prompting.md — GPT Image 2 composite prompt contract
reference/revise.md — revision workflow
reference/translate.md — localization workflow
reference/scrape.md — App Store scraping workflow

reference/create.md —— 端到端创建流程
reference/strategy.md —— 调研、策略简报、核心优势
reference/prompting.md —— GPT Image 2合成图提示词约定
reference/revise.md —— 修改工作流程
reference/translate.md —— 本地化工作流程
reference/scrape.md —— App Store爬取工作流程