lukas-hinterleitner/visual-app-skills

flutter-test-android-visually

Run a Flutter app on a connected Android device or emulator, capture real screenshots via adb, read the Dart + logcat logs, and verify the visible UI and runtime behavior match what a recent code change intended.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/lukas-hinterleitner/visual-app-skills --skill flutter-test-android-visually

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Flutter Android visual test

Interactive, on-device verification of a Flutter Android app — the "did my last change actually render correctly" check you'd otherwise do by squinting at an emulator. Builds and runs the app on a device or emulator, captures real screenshots via adb, reads the logs, and gives you enough evidence to answer did the change render correctly.

Works for any Flutter app, including multi-entry apps where the default entry point throws by design and a --target flag is mandatory. Android only — iOS needs a Mac and xcrun simctl, which is out of scope here.

When to use

  • "Test the app / run it on Android / see the visual changes."
  • "Did my UI fix work? Does this screen render correctly now?"
  • "Compare the capture screen to this Figma design." (optional Figma add-on)
  • Any request for empirical, on-device confirmation of a visual or runtime

change — even without the words "screenshot" or "logs".

How it works

  1. Follow `references/capture-loop.md` — the universal procedure: preflight,

launch in the background, wait for the first real frame, screenshot, capture logs, analyze the PNG against the change, report a verdict.

  1. For the Flutter specifics — the exact flutter run command and flags,

the first-frame log signal, where Flutter logs, hot reload, and cold-build timing — read references/flutter.md.

  1. To navigate the UI before screenshotting, see references/driving-the-ui.md.
  2. When something looks off, see references/troubleshooting.md.
  3. (Optional) compare to a Figma design → references/figma-comparison.md

(requires the Figma MCP server; skip entirely if you don't use Figma).

  1. Reached here with a non-Flutter Android app? See

references/other-frameworks.md or use the matching skill.

Bundled scripts

scripts/check-devices.sh, launch.sh, snap.sh, capture-logs.sh, stop.sh wrap the common adb/run commands with device disambiguation. capture-loop.md shows how they fit together.

Related by task