mobile-ui

Use when recording or re-recording screenshot-test baselines (golden images) in any Android/Compose project — Roborazzi, Paparazzi, or AGP's Compose Preview Screenshot Testing. Fire when the user says "record the baselines", "regenerate the screenshots", "update the snapshots", "the goldens are stale", or stages a new screenshot test with no images beside it. Skip when the project ships its own recording skill — that one knows its build's wiring. For checking existing baselines still pass, use android-screenshot-baseline-verify.

Use when checking that existing screenshot baselines still pass in any Android/Compose project — before pushing, after a refactor, a theme or design-token change, or a dependency bump. Fire when the user says "run the screenshots", "do the baselines still pass", "check the goldens", or asks whether a refactor changed the rendered output. Skip when the project ships its own verification skill. To create or update baselines rather than check them, use android-screenshot-baseline-record.

Use when a UI or behaviour change has to be confirmed on a running Android app rather than by a test — a setting that must take effect, a screen that has never been opened, a class the project cannot construct under Robolectric. Fire when the user says "check it on the device", "does it actually work", "run it and look", or when a change lands in a class that reaches Play Services and so has no unit-test seam. Fire also when a layout question has been answered twice from captures and the answer keeps moving, or when what is on screen depends on something a test cannot supply: a filled ad, a real inset, an orientation the manifest may lock away. Skip when a screenshot golden or a Robolectric test can hold the same claim — they are cheaper and they run in CI, which this never does.

Use when building or recreating a Jetpack Compose component from a Figma design in any Android project. Fire when a figma.com/design or figma.com/file link is paired with "build this", "implement this component", "recreate this in Compose", or a ticket references a Figma node id. Covers retrieving the node without flooding context, checking the design system before writing anything new, and binding to theme tokens rather than raw values. Skip when the project ships its own design-system skill — that one knows its component catalogue.