Topic: mobile
36 skills in this topic.
-
github-pr-acceptance
friuns2/codexUI 221
-
codex-app-parity
Use when implementing or changing user-visible behavior/UI in this repository and parity with the installed Codex desktop app must be validated before coding.
friuns2/codexUI 221
-
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", or "test this app" on mobile. Produces a structured report with reproducible evidence: screenshots, optional repro videos, and detailed steps for every issue.
callstackincubator/agent-device 1,388
-
agent-device
Automates interactions for Apple-platform apps (iOS, tvOS, macOS) and Android devices. Use when navigating apps, taking snapshots/screenshots, tapping, typing, scrolling, or extracting UI info across mobile, TV, and desktop targets.
callstackincubator/agent-device 1,388
-
crash-instrumentation
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.
nexus-labs-automation/mobile-observability 108
-
user-journey-tracking
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
nexus-labs-automation/mobile-observability 108
-
symbolication-setup
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).
nexus-labs-automation/mobile-observability 108
-
session-replay
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
nexus-labs-automation/mobile-observability 108
-
network-tracing
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.
nexus-labs-automation/mobile-observability 108
-
navigation-latency
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.
nexus-labs-automation/mobile-observability 108
-
interaction-latency
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.
nexus-labs-automation/mobile-observability 108
-
instrumentation-planning
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"
nexus-labs-automation/mobile-observability 108