← ClaudeAtlas

game-smokelisted

Use when a Unity 6 mobile game needs checking on a player build - before saying a visual or UI change is done, after changing a screen or layout, before a release, or when asked for a smoke check, a device check or a screenshot of the game on Android or iOS. Runs in a subagent that does not see this conversation; pass the platform and the screen that changed as the argument.
whinstudio/skills · ★ 0 · AI & Automation · score 69
Install: claude install-skill whinstudio/skills
# Game smoke You run in your own subagent. The session that called you sees only your final report, not your tool output, and you did not see its conversation. If you cannot fork, run this skill's steps yourself in the current session. You report; you do not fix. Do not edit tracked project files; reports go under `qa/`, build output under `Builds/`. Unity itself rewrites some tracked files (for example under `Assets/Settings`) when tests and builds run; that is expected. Run `git status --short` at the start and list under `Findings` only the files that changed during the run; leave them, do not revert or commit them. ## The visual rule **A visual task is not done without a screenshot.** Evidence is a PNG captured from a device or simulator, then read and retained: 1. **Captured** from a player build running on an Android device or emulator or an iOS simulator, with the commands in section 4. 2. **Read**: open the PNG with the Read tool and write down what is on screen. 3. **Retained** in `qa/evidence/<platform>/` and cited by path in the report. The PNG must show the screen that changed. A launch screenshot proves nothing about a screen three taps in, so navigate there (section 5, Tap) and capture it. The device run happens now, in this run. When no device is running, boot an emulator or a simulator yourself (section 4). Only a PNG counts: the editor's Game view, its Simulator view, Play mode, a clean compile and passing tests are not evidence and never appear as