mobile-app-debugging · aj-geddes — Claude Code skill: debug mobile apps
A skill for tracking down failures that only show up on a device: crashes, slow frames, flaky connectivity.
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a claude-codeWhat mobile-app-debugging does
The skill gives your agent context for mobile debugging. It covers three families of causes: platform quirks, device hardware limits, and mobile network conditions. The moment it earns its place is when an app dies on a phone but behaves in the simulator.
Inside is a short Xcode starting block: attach the debugger to a device, set breakpoints, step through execution, find device logs, and open the memory graph to hunt retain cycles. Deeper material sits in the references/ directory — one guide for iOS, one for Android, one for cross-platform cases, plus a testing checklist. The main file is SKILL.md.
This is not a replacement for native tooling. The panels and commands it names are Xcode's, so you still drive them yourself. Worth adding if your project ships a mobile build and you have already chased a bug that refuses to reproduce on desktop.
What it helps with
- trace a crash that happens on a physical device
- spot a retain cycle in the memory graph
- filter device logs down to one app
- tell a platform bug from a shared-code bug
- check how the app behaves on a weak connection
Example prompts for the agent
- The app crashes on launch on my iPhone, help me read the device log
- Open the memory graph and check the profile screen for retain cycles
- This bug only happens on Android, iOS is fine — where do I start
How to install mobile-app-debugging
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/mobile-app-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobile-app-debugging/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a codex2Manually: put the files in place
.agents/skills/mobile-app-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a cursor2Manually: put the files in place
.cursor/skills/mobile-app-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aj-geddes/useful-ai-prompts mobile-app-debugging2Manually: put the files in place
.github/skills/mobile-app-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/aj-geddes/useful-ai-prompts --path skills/mobile-app-debuggingManually: put the files in place
.devin/skills/mobile-app-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobile-app-debugging
How do I install mobile-app-debugging in Claude?
Run npx skills add aj-geddes/useful-ai-prompts --skill mobile-app-debugging -a claude-code. The skill file lands at ~/.claude/skills/mobile-app-debugging/SKILL.md.
What does mobile-app-debugging do?
It helps the agent work through mobile-specific failures: crashes, on-device performance problems, hardware constraints and network issues.
Which platforms does it support?
It installs into Claude, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode, each with its own install command.
Source text
SKILL.md · MIT
--- name: mobile-app-debugging description: > Debug issues specific to mobile applications including platform-specific problems, device constraints, and connectivity issues. --- # Mobile App Debugging ## Table of Contents - [Overview](#overview) - [When to Use](#when-to-use) - [Quick Start](#quick-start) - [Reference Guides](#reference-guides) - [Best Practices](#best-practices) ## Overview Mobile app debugging addresses platform-specific issues, device hardware limitations, and mobile-specific network conditions. ## When to Use - App crashes on mobile - Performance issues on device - Platform-specific bugs - Network connectivity issues - Device-specific problems ## Quick Start Minimal working example: ```yaml Xcode Debugging: Attach Debugger: - Xcode → Run on device - Set breakpoints in code - Step through execution - View variables - Console logs View Logs: - Xcode → Window → Devices & Simulators - Select device → View Device Logs - Filter by app name - Check system logs for crashes Inspect Memory: - Xcode → Debug → View Memory Graph - Identify retain cycles - Check object count - Monitor allocation growth --- Common iOS Issues: App Crash (SIGABRT): // ... (see reference guides for full implementation) ``` ## Reference Guides Detailed implementations in the `references/` directory: | Guide | Contents | |---|---| | [iOS Debugging](references/ios-debugging.md) | iOS Debugging | | [Android Debugging](references/android-debugging.md) | Android Debugging | | [Cross-Platform Issues](references/cross-platform-issues.md) | Cross-Platform Issues | | [Mobile Testing & Debugging Checklist](references/mobile-testing-debugging-checklist.md) | Mobile Testing & Debugging Checklist | ## Best Practices ### ✅ DO - Follow established patterns and conventions - Write clean, maintainable code - Add appropriate documentation - Test thoroughly before deploying ### ❌ DON'T - Skip testing or validation - Ignore error handling - Hard-code configuration values
© aj-geddes · MIT · aj-geddes/useful-ai-prompts
Similar skills
Everything for Mobile →mobile-app-debugging by other authors comes first.
