mobile-app-builder_skill

Overview

This skill helps build and maintain mobile applications end-to-end with OpenClaw, covering requirement shaping, architecture, implementation, debugging, testing, and release readiness. It emphasizes shipping small, testable increments, cross-platform default behavior, and clear validation steps. Use it to create new apps, add features, fix bugs, optimize performance, or prepare iOS/Android releases.

How this skill works

I start by clarifying the user goal into concrete acceptance criteria and constraints (platforms, backend, auth, timelines). I detect project mode (greenfield, feature, bugfix, refactor, or release hardening) and plan the smallest safe implementation slice. Changes are implemented incrementally—one coherent unit at a time—with type-safe code, preserved patterns, and minimal dependencies. Each task ends with validation commands, a concise change report, and follow-up risks or steps.

When to use it

• Create a new cross-platform mobile app or greenfield MVP.
• Add a feature to an existing React Native/Expo app with minimal disruption.
• Diagnose and fix mobile bugs with reproducible steps and regression tests.
• Improve performance or reduce bundle size for specific screens.
• Prepare and harden iOS/Android builds for distribution and signing.
• Validate release readiness: assets, deep links, permissions, and configs.

Best practices

• Prioritize small, testable increments over large rewrites.
• Default to cross-platform code (iOS + Android) unless requested otherwise.
• Reuse existing app patterns before adding new abstractions.
• Keep business logic out of view layers and prefer typed modules.
• List verification commands before coding and report exact outcomes.
• Avoid adding unused dependencies and limit native changes without approval.

Example use cases

• Scaffold a React Native + Expo MVP, core navigation, and one feature slice with typed API boundaries.
• Add a new settings screen reusing the app's existing state pattern and add validation/tests.
• Investigate a crash: reproduce, isolate root cause, add narrow logging, fix, and add regression coverage.
• Reduce initial bundle impact by deferring non-critical work and memoizing heavy computations.
• Prepare release builds: verify bundle identifiers, icons/splash assets, signing steps, and provide iOS/Android checklists.