Skip to content
Skillpedia
Mobile apps48k · #3074

mobile-games

Lets your agent understand how to make mobile games. It considers touch controls, battery life, and app store performance.

What it does

This skill helps you understand the challenges of creating games for mobile phones. It covers how touch controls work, how to save battery and prevent overheating, and what's needed to get your game into app stores.

When to use it

  • ✓When adapting a game to work well on mobile phones.
  • ✓When considering how players will interact with the game using touch.
  • ✓When preparing a game for publication on the App Store or Google Play.

Example of what to ask your AI

“Explain mobile game development principles to me.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/game-development/mobile-games/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/game-development/mobile-games/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The skill analyzes mobile limitations, like touchscreens and battery life, and suggests best practices for game optimization. It also lists basic requirements for publishing games on app stores.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill mobile-games

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/game-development/mobile-games/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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

  • Follow the platform accessibility target size (for example, iOS points and Android dp are different units)
  • Visual feedback on touch
  • Avoid precise timing requirements
  • Support the orientations chosen for the product; test rotation and safe areas where enabled

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 Required submission sizes for supported devices

Android (Google Play)

Requirement Note
Target API Current Play target-level deadline for this application
64-bit Required
App bundles Check mandatory format and exceptions for the submission

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.

When to Use

Use when adapting gameplay to touch controls, mobile interruptions, battery and thermal constraints, or preparing a store submission.

Example

User request:

Use @mobile-games for this task: Mobile game development principles.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Verification

Treat tables as design starting points, not guarantees. Prototype the selected mechanic, test accessibility and recovery paths, and measure frame timing, memory and behavior on target hardware before claiming completion. Store submission and licensing requirements must be checked against current official platform documentation.

FAQ

Why are touch controls different from computer controls?

Touch controls are less precise, cover part of the screen, and have fewer buttons. Mobile games need to be designed with this in mind, using larger touch areas and providing visual feedback.

How can a game save battery?

By reducing processor and graphics usage, avoiding unnecessary GPS or network use, and putting the game to sleep when not in play. Dark themes also help on OLED screens.

What are 'anti-patterns' in mobile games?

These are common practices that don't work well on mobile. Examples include using computer controls adapted for touch, ignoring phone overheating, or forcing the game to run only in landscape mode without player choice.

Details

Original description by the author

Mobile game development principles. Touch input, battery, performance, app stores.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#3074
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills