mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
Best use case
mobile-games is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Mobile game development principles. Touch input, battery, performance, app stores.
Teams using mobile-games should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mobile-games/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mobile-games Compares
| Feature / Agent | mobile-games | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Mobile game development principles. Touch input, battery, performance, app stores.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# 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.
Related Skills
mobile-design
Mobile-first design thinking and decision-making for iOS and Android apps. Touch interaction, performance patterns, platform conventions. Teaches principles, not fixed values. Use when building React Native, Flutter, or native mobile apps.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
2d-games
2D game development principles. Sprites, tilemaps, physics, camera.
async-python-patterns
Comprehensive guidance for implementing asynchronous Python applications using asyncio, concurrent programming patterns, and async/await for building high-performance, non-blocking systems.
slack-automation
Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.
linear-automation
Automate Linear tasks via Rube MCP (Composio): issues, projects, cycles, teams, labels. Always search tools first for current schemas.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
gitops-workflow
Complete guide to implementing GitOps workflows with ArgoCD and Flux for automated Kubernetes deployments.
github-automation
Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.
github-actions-templates
Production-ready GitHub Actions workflow patterns for testing, building, and deploying applications.