← LeaderboardThe Skill Leaderboard

mobile-games

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

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

mobile-games

Start a fresh conversation. Replace the highlighted placeholders.

Use mobile-games to review [mobile game concept] for [target platforms] and produce implementation recommendations for touch controls, responsive UI, battery and thermal performance, interruption handling, and app-store readiness.

Required inputs

  • [mobile game concept]
  • [target platforms]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: mobile-gamesdescription: "Mobile game development principles. Touch input, battery, performance, app stores."risk: safesource: communitydate_added: "2026-02-27"

Mobile Game Development

Platform constraints and optimization principles.


1. Platform Considerations

Key Constraints

ConstraintStrategy
Touch inputLarge hit areas, gestures
BatteryLimit CPU/GPU usage
ThermalThrottle when hot
Screen sizeResponsive UI
InterruptionsPause on background

2. Touch Input Principles

Touch vs Controller

TouchDesktop/Console
ImprecisePrecise
Occludes screenNo occlusion
Limited buttonsMany buttons
Gestures availableButtons/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

ActionTrigger
Reduce qualityDevice warm
Limit FPSDevice hot
Pause effectsCritical 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)

RequirementNote
Privacy labelsRequired
Account deletionIf account creation exists
ScreenshotsRequired submission sizes for supported devices

Android (Google Play)

RequirementNote
Target APICurrent Play target-level deadline for this application
64-bitRequired
App bundlesCheck mandatory format and exceptions for the submission

5. Monetization Models

ModelBest For
PremiumQuality games, loyal audience
Free + IAPCasual, progression-based
AdsHyper-casual, high volume
SubscriptionContent updates, multiplayer

6. Anti-Patterns

❌ Don't✅ Do
Desktop controls on mobileDesign for touch
Ignore battery drainMonitor thermals
Force landscapeSupport player preference
Always-on networkCache 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.