Mobile Game Development

VerifiedSafe

Mobile game development principles including touch input, battery optimization, performance targets, and app store requirements.

Sby Skills Guide Bot
DevelopmentIntermediate
7/25/2026
Claude CodeCursorWindsurf
#mobile-games#touch-input#performance-optimization#battery-optimization#app-store

Recommended for

Automated summary

This skill covers mobile game development principles, including platform constraints, performance optimization, and app store requirements.

Strengths

  • Provides concrete guidelines for touch targets and gestures
  • Addresses thermal management and battery optimization
  • Covers App Store and Google Play submission requirements

Limitations

  • Does not cover specific game engines like Unity or Unreal
  • Monetization strategies are high-level and not exhaustive
When to use it

Use this skill when developing a mobile game to ensure it meets platform constraints and store guidelines.

When not to use it

Avoid this skill if you are working on a desktop or console game, or if you already have deep mobile expertise.

Security analysis

Safe
Quality score85/100

The skill is purely informational, providing guidance on mobile game development. It does not instruct any code execution, system modifications, or network operations beyond the declared safe tools (Read, Write, Edit, Glob, Grep). No risky or destructive actions are present.

No concerns found

How this analysis is made

Examples

Touch input design
I need to design touch controls for my mobile game. What are the best practices for touch target sizes and gesture recognition?
Performance optimization
How can I optimize my mobile game for battery life and thermal throttling? Give me strategies for FPS targets and sleep modes.
App store compliance
What are the key requirements for publishing a mobile game on the App Store and Google Play? Include privacy labels and API targets.

name: mobile-games description: Mobile game development principles. Touch input, battery, performance, app stores. allowed-tools: Read, Write, Edit, Glob, Grep

Mobile Game Development

Platform constraints and optimization principles.


1. Platform Considerations

Key Constraints

| Constraint | Strategy | |------------|----------| | Touch input | Large hit areas, gestures | | Battery | Limit CPU/GPU usage | | Thermal | Throttle when hot | | Screen size | Responsive UI | | Interruptions | Pause on background |


2. Touch Input Principles

Touch vs Controller

| Touch | Desktop/Console | |-------|-----------------| | Imprecise | Precise | | Occludes screen | No occlusion | | Limited buttons | Many buttons | | Gestures available | Buttons/sticks |

Best Practices

  • Minimum touch target: 44x44 points
  • Visual feedback on touch
  • Avoid precise timing requirements
  • Support both portrait and landscape

3. Performance Targets

Thermal Management

| Action | Trigger | |--------|---------| | Reduce quality | Device warm | | Limit FPS | Device hot | | Pause effects | Critical temp |

Battery Optimization

  • 30 FPS often sufficient
  • Sleep when paused
  • Minimize GPS/network
  • Dark mode saves OLED battery

4. App Store Requirements

iOS (App Store)

| Requirement | Note | |-------------|------| | Privacy labels | Required | | Account deletion | If account creation exists | | Screenshots | For all device sizes |

Android (Google Play)

| Requirement | Note | |-------------|------| | Target API | Current year's SDK | | 64-bit | Required | | App bundles | Recommended |


5. Monetization Models

| Model | Best For | |-------|----------| | Premium | Quality games, loyal audience | | Free + IAP | Casual, progression-based | | Ads | Hyper-casual, high volume | | Subscription | Content updates, multiplayer |


6. Anti-Patterns

| ❌ Don't | ✅ Do | |----------|-------| | Desktop controls on mobile | Design for touch | | Ignore battery drain | Monitor thermals | | Force landscape | Support player preference | | Always-on network | Cache and sync |


Remember: Mobile is the most constrained platform. Respect battery and attention.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/mobile-game-development-mrzxupwi/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/mobile-game-development-mrzxupwi' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mobile-game-development-mrzxupwi/download' --output '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md.part' && mv '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md.part' '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Read, Write, Edit, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md' && test -s '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mobile-games' && cp -R '.skill-downloads/mobile-game-development-mrzxupwi' '.claude/skills/mobile-games'

Cursor
test -f '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md' && test -s '.skill-downloads/mobile-game-development-mrzxupwi/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/mobile-games' && cp -R '.skill-downloads/mobile-game-development-mrzxupwi' '.cursor/skills/mobile-games'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/mobile-game-development-mrzxupwi'

openskills read 'mobile-game-development-mrzxupwi'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/mobile-game-development-mrzxupwi/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills