Generate screenshots

A bare Save could be a button, a menu item, or a dialog title, and each reading translates differently. A screenshot is the strongest context Crowdin can attach to a string: Crowdin tags strings to positions on the image, so one screenshot contextualizes every string visible on it.

This skill owns the Crowdin side, the same on every platform: which screens are worth a shot, measured by which strings have none; one folder of PNGs whose file names are the screenshot identities; one upload; a report of what is still uncovered and why. Capturing is the platform's own business, done by a capture definition the skill writes into the project - a Playwright spec, Maestro flows, an XCUITest - so the next run is two commands. For every crowdin command's full behavior, read the crowdin-cli skill's commands reference; this file states only the flags it passes.

Preconditions

• A connected project: crowdin.yml with a project id and api_token_env, sources already uploaded - screenshots tag strings that exist in Crowdin. Without a crowdin.yml, the i18n-setup skill's connect-only path comes first.
• The Crowdin CLI, authorized. Exit code 101 means the user runs crowdin login in their own terminal; the token value stays out of the conversation.
• A shell. The engines and the CLI run in one. A connector-only assistant points the developer at this skill in a terminal.
• A runnable app and an engine from the table below, or publish-only mode without one.

The journey

1. Inventory. Measure before planning: