# Build and Improve Mobile Applications

Mobile teams must coordinate platform architecture, tooling, testing, performance, and release requirements. This skill provides practical guidance and examples for native and cross-platform workflows.

## Install

```bash
npx skillstore add zl2023github/mobile-engineer
```

## Metadata

- Status: approved
- Slug: zl2023github-mobile-engineer
- Skillstore revision: r2
- Version status: missing
- Tree hash: 5b62f7c97ac3cac238e33b793803bf8f7609e2f020e73f9aa1443e6cac05a4ab
- Author: zl2023github
- GitHub username: zl2023github
- License: MIT
- Repository: https://github.com/zl2023github/software-engineer-skills/tree/main/software-engineering/mobile-engineer
- Ref: 88a8e9a07f4c54ab105c1c41b6267c287146b07b
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands
- Quality score: 65
- Public page: https://skillstore.pages.dev/skills/zl2023github-mobile-engineer
- Manifest: https://skillstore.pages.dev/api/skills/zl2023github-mobile-engineer/manifest

## Capabilities

- Scaffolds Flutter and React Native projects with documented initialization commands and package recommendations.
- Recommends architecture patterns by project size for Flutter, React Native, Android, and iOS.
- Provides UI, networking, persistence, security, testing, and CI/CD guidance across supported stacks.
- Supplies build, test, cleanup, and release command references for major mobile platforms.
- Creates troubleshooting checklists for compilation failures, crashes, memory issues, and dependency conflicts.
- Suggests measurable performance checks for startup, rendering, application size, memory, and networking.

## Use Cases

- Start a Mobile Project: Select a stack, initialize the project, and establish architecture, navigation, storage, and networking foundations.
- Modernize an Existing Application: Review architecture, performance, security, and dependency choices before planning focused improvements.
- Prepare a Store Release: Build a release checklist covering tests, signing, privacy declarations, monitoring, metadata, and deployment automation.

## Prompt Templates

### Create a Starter Project

```
Create a [Flutter or React Native] project for [application type] with navigation, theming, and a clear folder structure.
```

### Implement a Mobile Feature

```
Implement [feature] for [platform], using the existing architecture and including loading, empty, error, accessibility, and test states.
```

### Diagnose a Performance Problem

```
Analyze [performance symptom] in this [platform] project, identify measurable causes, and propose benchmarks before and after each change.
```

### Design a Cross-Platform Release Plan

```
Design a secure release workflow for [iOS and Android], covering tests, signing, secrets, artifacts, staged rollout, monitoring, and rollback.
```

## Limitations

- The examples are reference patterns, not complete production applications.
- Project-specific guidance requires the target platform, framework, dependencies, and constraints.
- Package versions, mirror availability, and store requirements must be verified before use.
- Publishing still requires developer credentials, signing assets, store access, and human approval.

## Best Practices

- State the platform, framework version, existing architecture, and deployment target before requesting changes.
- Measure performance before optimization and define a repeatable benchmark for every proposed improvement.
- Review commands, dependency sources, signing changes, and release actions before execution.

## Anti Patterns

- Do not request a complete application without product requirements, platform constraints, or acceptance criteria.
- Do not copy sample endpoints, credentials, package versions, or signing settings directly into production.
- Do not run cleanup, installation, build, or publishing commands without reviewing their scope and side effects.

## Security Audit

- Audited at: 2026-07-23T23:41:42.171\+00:00
- Summary: All 55 static alerts are false positives caused by Markdown syntax, mobile tool names, explicit HTTPS examples, and a fixed Xcode cache path. No prompt injection, credential exposure, obfuscated payload, host reconnaissance, or unbounded root deletion appears in the reviewed files. Semantic review identified unpinned package execution and unconditional response-body logging as medium risks.

## Stats

- Views: 1
- Downloads: 5
- Favorites: 0
- Popularity score: 0