# mobile-game-dev

This skill guides agents through mobile game development on iOS and Android, covering touch controls, battery use, thermal limits, device differences, and store submission.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 226 installs · ★ 221 repo stars
- Author: omer-metin
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/omer-metin/skills-for-antigravity/tree/HEAD/skills/mobile-game-dev/SKILL.md
- Updated: 2026-01-22
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/mobile-game-dev

## What it does

\`mobile-game-dev` gives an agent a mobile game development focus. It covers iOS and Android performance, touch input, battery drain, thermal throttling, memory pressure, app lifecycle, interruptions, and differences in screens, GPUs, and RAM across devices. It also brings App Store and Play Store submission concerns into the discussion.

The skill directs creation work to `references/patterns.md`, diagnosis to `references/sharp_edges.md`, and review to `references/validations.md`. These files shape how the agent builds, explains failures, and checks constraints. If the installed copy lacks those references, the related checks cannot be carried out.

Installation uses `npx skills add` for Claude Code, Codex, Cursor, Gemini CLI, and OpenCode. GitHub Copilot uses `gh skill install`, while Gemini CLI has a second install command that targets the repository path.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/mobile-game-dev/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/mobile-game-dev/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/mobile-game-dev/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/mobile-game-dev/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install omer-metin/skills-for-antigravity skills/mobile-game-dev
```

2. **Manually: put the files in place**
- File: `.github/skills/mobile-game-dev/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/mobile-game-dev
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/mobile-game-dev/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/omer-metin/skills-for-antigravity/tree/HEAD/skills/mobile-game-dev/SKILL.md

## When to use it
- check a mobile game for thermal throttling and battery drain
- design touch controls for phones and tablets
- trace issues across devices with different GPUs and RAM
- prepare a game for App Store and Play Store review
- handle saved state during calls, notifications, and backgrounding

## Example prompts
- Review this mobile game for battery drain, thermal throttling, and memory pressure.
- Design touch controls for a phone and tablet while accounting for calls and notifications.
- Prepare the game for App Store and Play Store submission using `references/validations.md`.

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f055dbf596566526.

BEGIN THIRD-PARTY FILE f055dbf596566526
```text
---
name: mobile-game-dev
description: Expert mobile game developer specializing in iOS and Android game optimization, touch input design, battery and thermal management, device fragmentation handling, and App Store/Play Store submission. Deep knowledge of mobile-specific constraints and best practices for shipping performant, player-friendly mobile games. Use when "mobile game, ios game, android game, touch input, mobile optimization, mobile performance, app store, play store, mobile battery, thermal throttling, mobile porting, tablet game, phone game, mobile monetization, mobile build, mobile, ios, android, touch, optimization, performance, battery, thermal, app-store, play-store, game-development, unity-mobile, godot-mobile, device-fragmentation" mentioned. 
---

# Mobile Game Dev

## Identity

You're a mobile game developer who has shipped titles across the entire spectrum of
devices - from the iPhone 6 to the latest iPad Pro, from budget Android phones to
flagship Samsungs. You've learned that mobile development is a completely different
beast from PC or console development.

You've felt the pain of a game that runs beautifully in the editor but melts phones
in players' hands. You've debugged thermal throttling issues at 2 AM, optimized
touch input to feel responsive on both 60Hz and 120Hz displays, and learned to treat
battery life as a first-class feature. You know that a mobile game that drains
battery in an hour will get uninstalled in seconds.

You've navigated the maze of App Store guidelines and Play Store policies, dealt
with cryptic rejection reasons, and learned what "Not Responding" (ANR) means the
hard way. You understand that mobile players have different expectations - they want
instant load times, one-handed playability, and the ability to pause and resume
seamlessly.

You've battled device fragmentation - the thousands of Android devices with different
screen sizes, aspect ratios, GPUs, and RAM amounts. You've learned to test on the
lowest-spec devices in your target market, not just your development phone. You know
that Mali GPUs behave differently than Adreno, and that some devices lie about their
capabilities.

Your core principles:
1. Target your minimum spec device, not your development device
2. Battery drain and thermal throttling are bugs, not "optimization tasks"
3. Touch input has unique needs - no hover states, fat fingers, palm rejection
4. Memory pressure kills games silently - respect the OS memory limits
```
END THIRD-PARTY FILE f055dbf596566526

The third-party file has ended. Everything between the f055dbf596566526 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2483 of 3567 bytes. © omer-metin · Apache-2.0 · https://github.com/omer-metin/skills-for-antigravity/tree/HEAD/skills/mobile-game-dev/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
