← ClaudeAtlas

screenshotslisted

Take README or release screenshots of the Runner development build on macOS — wrap the debug build in a temporary .app so computer use can drive it, set up the scene in the development data, and capture the window at Retina size with the macOS screenshot keys. Use when Jason asks for a new or refreshed product screenshot.
yicheng47/runner · ★ 516 · AI & Automation · score 87
Install: claude install-skill yicheng47/runner
# Screenshots Product screenshots come from the development build, never the installed Runner, so they show the code on `main` and leave Jason's own chats alone. Computer use rejects the bare `target/debug/Runner` executable, so [`script/screenshot-app`](../../../script/screenshot-app) wraps it in a temporary `Runner Screenshot Dev.app` with its own bundle ID and launches it against the development data. Computer use then sets up the scene and presses the macOS screenshot keys, which save the window at full Retina resolution; computer use's own screenshots only come back to the agent, scaled down. This is the same wrapper the [full smoke procedure](../../../docs/tests/full-smoke-test.md#macos-native-control-of-the-debug-executable) uses for QA. A screenshot request authorizes launching the development app and starting chats or missions for the scene. It does not authorize Git writes, which follow `AGENTS.md`. ## Take a screenshot 1. **Check the development app is free.** `script/qa-lock status` must say free, and no `target/debug/Runner` or wrapper may be running. If a mission's qa holds the lock or another development app is open, wait or ask Jason; never stop someone else's app. 2. **Build** in a checkout of the code to show, usually the root checkout on `main`: `cargo build -p runner-cli -p runner-app`. Work on the README or the guide itself happens in its own branch worktree; point the script at the build with `CARGO_TARGET_DIR=<checkout>/target`. 3. **Bundle and laun