mobile-game-dev — Claude Code skill: what it does, how to install
This skill guides agents through mobile game development on iOS and Android, covering touch controls, battery use, thermal limits, device differences, and store submission.
Apache-2.0 226 installs ★ 221 updated 2026-01-22
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a claude-codeWhat mobile-game-dev 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.
What it helps with
- 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 for the agent
- 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.
How to install mobile-game-dev
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a claude-code2Manually: put the files in place
~/.claude/skills/mobile-game-dev/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mobile-game-dev/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a codex2Manually: put the files in place
.agents/skills/mobile-game-dev/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a cursor2Manually: put the files in place
.cursor/skills/mobile-game-dev/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install omer-metin/skills-for-antigravity skills/mobile-game-dev2Manually: put the files in place
.github/skills/mobile-game-dev/SKILL.md1Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a gemini-cli2Platform CLI
gemini skills install https://github.com/omer-metin/skills-for-antigravity --path skills/mobile-game-devManually: put the files in place
.devin/skills/mobile-game-dev/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about mobile-game-dev
How do I install mobile-game-dev in Claude Code?
Run npx skills add omer-metin/skills-for-antigravity --skill mobile-game-dev -a claude-code, then check ~/.claude/skills/mobile-game-dev/SKILL.md.
What does the mobile-game-dev skill do?
It guides agents on mobile-specific game work, including touch input, battery use, thermal limits, memory, app lifecycle, device fragmentation, and App Store or Play Store submission.
Which reference files does mobile-game-dev use?
Creation work uses references/patterns.md, diagnosis uses references/sharp_edges.md, and review uses references/validations.md.
Source text
SKILL.md · Apache-2.0
--- 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 5. App lifecycle is your friend - save state, pause audio, release resources 6. Profile on real devices, every sprint, on the worst device you support 7. First-time user experience (FTUE) must load in under 5 seconds 8. 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.
© omer-metin · Apache-2.0 · omer-metin/skills-for-antigravity