mobile-teamlisted

Deploy the mobile agents (mobile-app-builder, mobile-ux-optimizer) — with ui-designer/ux-researcher/frontend-developer on call — to design and build native or cross-platform mobile apps. Advisory-first for UX, build-and-verify for the app. Use standalone ("build the iOS app", "optimise this screen for mobile") or as the mobile lane inside a plan. Nascent — a growth area for the planned web+mobile package.
hjr15/claude-kit · ★ 0 · Web & Frontend · score 76

Install: claude install-skill hjr15/claude-kit

# /mobile-team — Native & Cross-Platform Mobile ## Overview The mobile lane, distinct from the web `frontend-team`: | Agent | Role | |---|---| | `mobile-app-builder` | **Builds** — native iOS (Swift/SwiftUI) / Android (Kotlin/Compose) + cross-platform (React Native, Flutter, Expo); 60fps, platform integration, offline-first, app-store readiness | | `mobile-ux-optimizer` | **Mobile UX** — touch targets, thumb-zone/one-handed flows, mobile-first layouts, theme consistency | | `ui-designer` / `ux-researcher` (on call) | shared visual/UX judgement (web + mobile) | | `performance-engineer` (on call) | mobile profiling (frame rate, memory, battery, startup) | > **Status: nascent.** There are no mobile apps in the repos yet — this team exists > for the **planned web+mobile package**. It's a deliberate growth area: as real > mobile work starts, expect to add agents (e.g. release/store management, mobile > CI/CD, deep-link/push specialists) and to harden the conventions. Treat it as a > seed, not a finished unit. ## When to Use - Building or designing a native/cross-platform app, or a mobile screen/flow. - Deciding a mobile architecture (native vs RN vs Flutter) — pull `architect-team` too. - Not for: mobile-*responsive web* (that's `frontend-team` + `ui-designer`, which now carries the mobile-first responsive specifics). ## Adaptive agent selection (token discipline) - *UX/usability of a mobile screen* → `mobile-ux-optimizer` (+ `ux-researcher`). - *build/implement a feature*