Use app context before asking for screenshots
A screenshot set can start from the project you are already building. Real captures and missing-screen placeholders remain distinct.
A small, evidence-based brief
The skill uses the authorized task and relevant project information to summarize purpose, audience, brand, platform and the screen sequence. Features observed at runtime, features seen only in source, and proposed features must not be treated as equally verified. The remote service receives the selected brief, not automatic access to the repository.
Capture only an existing runnable setup
- Web: use an available host browser or an already installed Playwright/repository capture runner.
- iOS: use existing simulator and navigation tooling with the matching app already runnable.
- Android: use an already authorized emulator or device with existing adb/test tooling.
Available tools and host permissions determine what can run. Missing credentials, toolchains or app states should lead to a storyboard, not a guessed login, new deployment or remote build. Capture with appropriate local sample data and inspect images for private information before transfer.
When a capture is missing
The set keeps an editable placeholder labeled with the needed app state. Later captures can replace those placeholders while preserving the design. A draft containing placeholders must not be described as ready for store upload.
The built-in browser is available on supported desktop surfaces, not every CLI or IDE host. See the official browser documentation.