The detail in the goldie README that matters to me is where the work lives. The screenshots and preview videos are rendered output, while the inputs are files in your app repo that a coding agent can write and then edit again when you ask for a change.
What the pipeline covers
goldie makes App Store and Google Play screenshots, plus App Store preview videos, for a mobile app. The README splits the job across two tools. argent replays flows on an iOS simulator or an Android emulator. goldie frames the captures with a device bezel, a background and a headline, joins the clips into a preview video, and checks the result against the upload rules of the stores.
Since it drives the app through the simulator or the emulator, the README calls goldie framework agnostic and says it works the same for SwiftUI, UIKit, Jetpack Compose, Flutter, React Native and Kotlin Multiplatform apps.
To run it by hand, you copy goldie.config.example.ts to goldie.config.ts, point its scenes at argent flows in .argent/flows, and use three commands. goldie doctor checks tools, simulators and flows. goldie all captures, frames, renders the preview and verifies. goldie studio lets you preview and tweak the assets in the browser. Output lands in out/screenshots/<device>/<locale>/ and out/previews/<device>/<locale>/. Per the README, the iPhone gets 1320 x 2868 screenshots and an 886 x 1920 H.264 preview, Google Play gets 1080 x 1920 screenshots, and an App Store preview must run 15 to 30 seconds.
The agent writes the inputs
The first usage section in the README is a sentence typed into a coding agent from the app repo: create app store screenshots using goldie. The agent asks which stores to target, explores the app, writes the flows and the config, and opens the studio. Follow-ups such as use a dark background edit the same files.
That last line is the one I would hold onto. The studio switches devices, backgrounds, templates, bezel, fonts and per-tile copy, and it saves those choices to goldie.design.json, so the CLI renders the same result. A tweak made in the browser carries over to the next CLI run, and a later request to the agent lands in the files the agent already wrote.
Installation comes in two parts. The CLI installs with npm i -g goldie. The skill goes in with npx skills add kacperkapusciak/goldie for Cursor, Codex or other agents, or with /plugin marketplace add kacperkapusciak/goldie followed by /plugin install goldie@goldie in Claude Code. The README says the skill works with all agents that support the skills format.
The config also takes several design settings directly. frame takes 17-pro-blue, 17-pro-silver, 17-pro-orange or a custom bezel image, and theme.screenOnly: true removes it. theme.template accepts named templates such as editorial or storyboard, or your own sequence of layouts like hero, tilt and panorama-duo. theme.fontFamily is a CSS font stack, and decorations layers badges or images behind the device.
What it needs from your machine
Requirements depend on the store you target. You need Node 20 or newer and ffmpeg on the PATH. App Store screenshots need macOS with iOS simulators (Xcode). Google Play screenshots need an Android emulator, which the README says works on macOS, Linux and Windows, and on Linux argent needs a few extra packages for Android emulators. On a Linux or Windows machine you keep only pixel-10-pro in devices, and goldie doctor tells you so when an iOS device is configured on a host that cannot run it.
Android brings its own constraints. The emulator's AVD must use the Pixel 10 Pro or the Pixel 9 Pro hardware profile. goldie reuses a running emulator that matches, or boots the AVD itself, and the config needs an android block with appPath and applicationId. The scene flows are shared between platforms, and a flow works on both when its selectors match. Android tiles get the bundled Pixel 10 Pro bezel. The frame variant is iPhone art, so it does not apply to them, and android.frame swaps in your own art and its geometry.
The Play Store promo video is a YouTube link, so preview and all record the preview scene on the emulator and render a portrait video that you post on YouTube yourself. Apple's 15 to 30 second window does not apply to it.
Where it breaks
The Remarks section lists two caveats. Use a Release build, because Debug builds paint LogBox banners into the captures. And flows fail when the app changes; the README suggests asking the coding agent to repair them, or re-recording them with argent.
That second caveat is worth thinking about before you put goldie into a release routine. If your screens shift every sprint, plan for flow repair as a recurring task alongside the asset refresh.
GitHub: https://github.com/kacperkapusciak/goldie
Curated by Agent Palisade — practical AI for small and mid-sized businesses.
Top comments (0)