القائمة
Capture quick Android UI evidence with explicit launches, UIAutomator dumps, and adb screenshots for fast visual debugging and reproducible repro notes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | android-ui-automator-preview |
| description | Capture quick Android UI evidence with explicit launches, UIAutomator dumps, and adb screenshots for fast visual debugging and reproducible repro notes. |
| argument-hint | Provide the full application ID, target screen, and whether app data should be cleared first |
pm clear.uiautomator dump or scale them from the recorded 1080x2400 @ 420dpi baseline.adb devices -l
adb logcat -c
# Only run when the user explicitly asks to clear app data:
# adb shell pm clear <package-name>
adb shell am start -n <package-name>/co.anitrend.android.deeplink.component.screen.DeepLinkScreen
Why:
<package-name> with the application ID for the installed build.monkey randomness.These coordinates are a recorded baseline for 1080x2400 @ 420dpi only.
Re-derive coordinates from a fresh uiautomator dump before using them on a
different device or resolution.
# Recorded baseline only - re-derive for your device:
# adb shell input swipe 900 1700 200 1700 300 # onboarding page 1 -> 2
# adb shell input swipe 900 1700 200 1700 300 # onboarding page 2 -> 3
# adb shell input swipe 900 1700 200 1700 300 # onboarding page 3 -> 4
# adb shell input swipe 900 1700 200 1700 300 # onboarding page 4 -> 5
# adb shell input tap 540 2280 # tap Get Started
# adb shell input tap 540 1285 # tap Allow
# Recorded baseline only - re-derive for your device:
# adb shell input tap 84 2240
adb shell uiautomator dump /sdcard/window_dump.xml
adb pull /sdcard/window_dump.xml /tmp/window_dump.xml
adb exec-out screencap -p > /tmp/screen.png
grep -E "General|Manage|Catalogs|Support|Home|Discover|News|Forums|Episodes|FAQ" /tmp/window_dump.xml
pid=$(adb shell pidof -s <package-name> | tr -d '\r')
adb logcat -d --pid="$pid" > /tmp/<package-name>-ui-window.log
Use ADB to connect devices, install Android debug builds, and troubleshoot deployment failures. Use for device detection errors, install failures, launch failures, package selection across flavors, and first-pass process checks. For deeper runtime investigation, prefer the Argent workflow.
Android platform/helper layer guide for AniTrend. Use when working in `:android:*` modules or deciding whether to reuse or extend existing Android-side helpers for configuration/theme, context or fragment utilities, notification permission flows, deep links, drawer/app-shell behavior, or other platform APIs.
Investigate Android runtime bugs with evidence-first workflows. Use for emulator targeting, logcat/AndroidRuntime/Timber inspection, Chucker HTTP/GraphQL payloads, UIAutomator hierarchy capture, Room database forensics, and root-cause analysis before changing code.
Use when planning or thinking of AniTrend brand identity UI & UX covering compose screens, various surfaces, interaction-heavy UI, layout hierarchy, component decomposition, preview strategy, Material3 layering, or incremental product-facing refactors before coding.
Diagnose and fix silent empty-UI bugs caused by CacheRequest enum collisions in AniTrend. Use when a new offline-first source variant produces blank UI with no crash, no exception, and the Room tables have zero rows. Covers: cache_log collision diagnosis, ADB Room database forensics, WAL checkpoint, Chucker traffic check, CacheRequest isolation fix, and Koin factory update pattern.
data/android module reference. Use when working with ControllerStrategy, OnlineStrategy, OfflineStrategy, ScopeExtensions, graphQLController Koin wiring, DefaultController, DeferrableNetworkClient, ICacheStore, or when asking what the data/android module provides to other data modules and why it is a shared dependency.