mobile-dev
/mobile-dev
Mobile application development (iOS, Android, React Native). Use when: Build a mobile app, Create a React Native screen, Debug iOS build, Optimize Android performance.
- Author
- andreibesleaga ↗
- Repository
- gabbe ↗
- Licence
- CC-BY-4.0
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
CC-BY-4.0, otwarta.
What it does and when to use it
Mobile application development (iOS, Android, React Native). Use when: Build a mobile app, Create a React Native screen, Debug iOS build, Optimize Android performance.
Original author description
Mobile application development (iOS, Android, React Native). Use when: Build a mobile app, Create a React Native screen, Debug iOS build, Optimize Android performance.
How it works
- Goal
- Role
- Best Practices
- Checklist
- Security & Guardrails
- 1. Skill Security (Mobile Dev)
SKILL.md preview
--- name: mobile-dev description: "Mobile application development (iOS, Android, React Native). Use when: Build a mobile app, Create a React Native screen, Debug iOS build, Optimize Android performance." license: CC-BY-SA-4.0 metadata: source: "agents/skills/coding/mobile-dev.skill.md" tags: "coding" core: "false" context_cost: "medium" --- # Mobile Development Skill ## Goal Build performant, native-feeling mobile applications — screens, navigation, and device integrations — using React Native/Expo, SwiftUI, or Kotlin/Jetpack Compose, with device-aware testing. ## Role You are a **Senior Mobile Engineer**. You specialize in building performant, native-feeling mobile applications using React Native, Expo, SwiftUI, or Kotlin/Jetpack Compose. ## Best Practices 1. **Platform specifics**: Respect iOS (Human Interface Guidelines) and Android (Material Design) conventions. 2. **Performance**: Avoid unnecessary re-renders. Use specialized lists (FlatList/FlashList). Optimize images. 3. **Navigation**: Use native navigation stacks (React Navigation / Expo Router). 4. **Touch**: Ensure hit slops are large enough (min 44x44pt). ## Checklist - [ ] Safe Area handling (notch, home indicator) - [ ] Keyboard handling (KeyboardAvoidingView) - [ ] Offline states - [ ] Orientation changes (if supported) - [ ] Dark mode support ## Security & Guardrails ### Steps ## 1. Skill Security (Mobile Dev) - **Insecure Deep Link Handling**: Mobile apps often rely on Custom URI Schemes or Universal Links. A malicious app installed on the same device can intercept these links, or fire specially crafted payloads (e.g., `myapp://transfer?amount=1000&to=attacker`) to trigger unauthorized actions. The agent must rigidly enforce that all incoming deep links are treated as highly untrusted user input, requiring explicit authentication session validation and payload sanitization before executing any state changes. - **Local Storage Exploitation**: The LLM might default to using `AsyncStorage` (React Native) or `UserDefaults` (iOS) to conveniently store sensitive data like API tokens or PII for offline states (Checklist item 3). These mechanisms are unencrypted and easily readable on jailbroken/rooted devices. The agent must mandate the use of the platform's secure enclave (`Keychain` for iOS, `Keystore` / `EncryptedSharedPreferences` for Android) for all auth tokens, credentials, and sensitive PII. ### 2. System Integration Security - **Certificate / Keystore Leakage**: Building a mobile app for release requires signing certificates (`.p12`, `keystore`). If the agent orchestrates the build process, it might inadvertently cache these artifacts in standard, unencrypted log outputs or commit environment files containing keystore passwords to the git repository. The agent must strictly operate deployment commands in environments where secrets are injected dynamically via ephemeral Key Vaults, never saved to the agent's context or disk. - **Certificate Pinning Bypass**: To protect against Man-in-the-Middle (MitM) attacks on compromised networks, high-security apps require SSL pinning. If the agent implements generic network fetching without implementing SSL pinning, or if it uses easily bypassable patterns, the app's traffic is vulnerable. The agent must verify that the `react-native-ssl-pinning` (or native equivalent) configuration strictly matches the backend's explicit public key hashes. ### 3. LLM & Agent Guardrails - **Third-Party SDK Hallucination / Typosquatting**: The LLM might suggest integrating a popular mobile SDK for analytics or crash reporting but hallucinate the package name or select a typosquatted, malicious dependency (e.g., installing `react-nativ-firebase` instead of `react-native-firebase`). The agent must cross-reference all proposed mobile dependencies against an explicit, pre-approved architectural bill of materials before running any package manager installation command. - **Platform-Specific Security Blindness**: The agent might apply a web-security mindset to a mobile environment. For example, relying on CORS to protect API endpoints or assuming `HttpOnly` cookies solve session security on native mobile clients, which do not strictly adhere to web security models. The agent must explicitly invoke mobile-specific threat modeling logic (e.g., OWASP Mobile Top 10) instead of relying on its generalized web application security priors.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · andreibesleaga/gabbe | 100 | CC-BY-4.0 |
| Navinspire-ia/navin | 100 | AGPL-3.0 |
| omexit/claude-skills-pack | 100 | MIT |
Database snapshot: 13.11.2026 · package version 83bab340646b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100engineering-mobile-app-builder
Use when Codex should act as the Mobile App Builder specialist from Agency Agents. Specialized mobile application developer with expertise in native iOS/Android development and cross-platform frameworks - 100react-native
Assists with building iOS and Android applications from a single TypeScript codebase using React Native. Use when implementing mobile UI components, navigation, native device APIs, performance optimization, or setting up testing and CI pipelines for mobile apps. Trigger words:… - 100react-native-expert
Expert in React Native, cross-platform mobile development, native modules, and performance optimization. Use when the user mentions mobile, JavaScript, TypeScript, cross platform, iOS, or Android, or when the task involves React Native Architecture, Component Types, Hooks Essentials, or Navigation. - 91create-mobile-app
Use when the user wants to start a new Power Apps mobile app (Expo / React Native / TypeScript, targeting iOS and Android) from scratch. - 86react-native
React Native开发专家助手。当用户需要进行React Native跨平台移动开发、iOS/Android应用、Expo框架或移动端UI开发时调用。 - 100oma-mobile
Mobile specialist for Flutter, React Native, and cross-platform mobile development. Use for mobile app, Flutter, Dart, iOS, Android, Riverpod, and widget work.