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.
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. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## 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.
Related Skills
epic-games-automation
Automate Epic Games tasks via Rube MCP (Composio). Always search tools first for current schemas.
mobile-security-coder
Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns.
mobile-developer
Develop React Native, Flutter, or native mobile apps with modern architecture patterns. Masters cross-platform development, native integrations, offline sync, and app store optimization.
mobile-design
(Mobile-First · Touch-First · Platform-Respectful)
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.
frontend-mobile-security-xss-scan
You are a frontend security specialist focusing on Cross-Site Scripting (XSS) vulnerability detection and prevention. Analyze React, Vue, Angular, and vanilla JavaScript code to identify injection poi
frontend-mobile-development-component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, s
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".