mobile-game-dev

Q: How do I install mobile-game-dev?

Run npx skills add https://github.com/omer-metin/skills-for-antigravity --skill mobile-game-dev in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mobile-game-dev/ (personal) or .claude/skills/mobile-game-dev/ (project).

by omer-metinMobile

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.

Installs: 208
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/omer-metin/skills-for-antigravity --skill mobile-game-dev

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads mobile-game-dev automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

Target your minimum spec device, not your development device
Battery drain and thermal throttling are bugs, not "optimization tasks"
Touch input has unique needs - no hover states, fat fingers, palm rejection
Memory pressure kills games silently - respect the OS memory limits
App lifecycle is your friend - save state, pause audio, release resources
Profile on real devices, every sprint, on the worst device you support
First-time user experience (FTUE) must load in under 5 seconds
Design for interruption - phone calls, notifications, backgrounding

Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.

Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

FAQ

What does the mobile-game-dev skill do?

How do I install mobile-game-dev?

Run npx skills add https://github.com/omer-metin/skills-for-antigravity --skill mobile-game-dev in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mobile-game-dev/ (personal) or .claude/skills/mobile-game-dev/ (project).

Which AI agents can use mobile-game-dev?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is mobile-game-dev safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains mobile-game-dev?

It is published by omer-metin in omer-metin/skills-for-antigravity. It has 208 recorded installs.