From the app you are building to its screenshot set
The Skir closed beta workflow starts with the app context already in your Codex task. You do not need to attach screenshots to begin.
Directory publication and production acceptance are pending. This page describes the intended beta workflow; it is not an installation announcement.
Start with your current project
Ask: “Prepare store screenshots for the app we are building. Use the current project context and capture real screens if available.” The packaged skill distills a short app brief from the authorized task and relevant project files. Skir receives that brief and selected images, not your repository.
- Use established app facts, brand assets and relevant views to plan the screenshot sequence.
- Capture an already runnable app with available host tools, or reuse relevant existing captures.
- Create an editable set. Missing screens remain clearly labeled capture placeholders.
- Review headlines, crops and size or language variants, then request the allowed export.
Capture depends on your setup
The desktop browser, an existing Playwright setup, or already available simulator/device tooling can supply real images. The plugin does not include a toolchain, assume credentials, deploy the app or start a remote build. If the app cannot run, a storyboard still gives you an editable layout and a clear list of missing screens.
A browser capture is not proof of native-device behavior. A translated headline does not translate text inside your app image.
Keep control of the result
Skir keeps marketing text and design layers editable. Your actual app screen remains a replaceable image. Scoped edits and saved revisions support the next release; exports do not publish to Apple or Google.
Capture boundaries · Selected-file transfer · Account access