Skill
acceptance-orchestrato…
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human…
@sinhoneyyView SkillDevelopment
Skill
/mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
Install
$ npx -y skills add sinhoneyy/master-skills --skill mobile-games --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/mobile-games
Context preview
The summary Claude sees to decide when to auto-load this skill.
Mobile game development principles. Touch input, battery, performance, app stores.
SKILL.md
mobile-games.SKILL.mdname: mobile-games
description: "Mobile game development principles. Touch input, battery, performance, app stores."
risk: safe
source: community
date_added: "2026-02-27"
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.
Read more
name: mobile-games description: "Mobile game development principles. Touch input, battery, performance, app stores." risk: safe source: community date_added: "2026-02-27"
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.
Ships withmaster-skills
Unified skill library for Claude, Codex, Cursor, Antigravity & AI agents — 2,658 skills across 15 domains
Get the whole plugin
Stats
12
Stars
3
Forks
Active
Maintenance
Python
Language
13d ago
Last commit
3mo ago
Created
Repo: sinhoneyy/master-skills
Other skills on master-skills.
@sinhoneyyView SkillSkill
accesslint-audit
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix…
@sinhoneyyView SkillSkill
activecampaign-automat…
Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first…
@sinhoneyyView SkillSkill
adhx
Fetch any X/Twitter post as clean LLM-friendly JSON. Converts x.com, twitter.com, or adhx.com links into structured data with full article content, author…
@sinhoneyyView SkillSkill
advanced-evaluation
This skill should be used when the user asks to "implement LLM-as-judge", "compare model outputs", "create evaluation rubrics", "mitigate evaluation bias", or…
@sinhoneyyView SkillSkill
aegisops-ai
Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance.
@sinhoneyyView Skill