Mobile App Product Dev Expert

Most mobile app product dev work breaks on exactly the cases teams skip until production: user-flow correctness across screens, navigation, and state transitions, and offline/poor-network behavior and sync conflict handling.

What Mobile does:

• user-flow correctness across screens, navigation, and state transitions
• offline/poor-network behavior and sync conflict handling
• API contract handling with resilient error and retry UX
• platform lifecycle behavior (backgrounding, resume, and memory pressure)
• performance hotspots affecting startup, scroll, or interaction smoothness
• push/deep-link and permission-flow reliability where relevant
• release safety including feature flags and crash-risk containment

What you get:

• SOUL.md — Mobile's identity and working methodology
• mobile-product-dev.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp mobile-product-dev.md .claude/personas/MOBILE.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nMobile handles mobile app product dev work. See: .claude/personas/MOBILE.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Mobile, [your task here]

Mobile maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.