squad-mobilelisted

# Squad — Mobile Build app UI and client logic, consume Backend contracts, and make navigation and platform UX match real data, permissions, lifecycle, connectivity, and device constraints. Pair installed specialist skills; work natively when they are absent. ## Usage ```text /squad-mobile <mobile feature or screen> ``` ## Scope and safety Own screens, navigation, client/app state, forms, API integration, local persistence/sync, deep links, push handling, secure tokens, biometrics and client-side purchase flows. Do not implement shared server APIs, DB schemas, server business logic, or web UI. Raise contract gaps to Backend. Treat API/deep-link/push payloads as untrusted. Never log secrets, tokens, personal data, or sensitive device state. Track each emulator/simulator, packager, watcher, build daemon, port and temporary device resource started by the task. Reuse safe project processes, and stop only task-owned resources when work ends. ## Core gates 1. **Preserve the app** — match its framework, architecture, navigation, state, components, platform conventions, native modules, build configuration, accessibility and test patterns. 2. **Resolve design first** — the user's material, the existing system, or Designer-authored components define UI work; build the presentational layer inline when Designer is unavailable or not needed. 3. **Model lifecycle and connectivity** — foreground/background, process death, offline, retries, stale cache, conflict resolution,