AGENT SKILL

mobile-games

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

License 许可
MIT
最近更新
2026-07-29
Stars
★ 0
Forks
0

01 前言 Front Matter

name
mobile-games
description
Mobile game development principles. Touch input, battery, performance, app stores.
allowed-tools
Read, Write, Edit, Glob, Grep

03 SKILL.md 正文

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.

04 同仓库更多 Skills

KrismithReddy12
KrismithReddy12/claude-code-templates

zapier-make-patterns

No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points. This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

yeet

Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

workflow-automation

Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off. This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation. Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

trigger-dev

Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

slack-automation

Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.

★ 0
KrismithReddy12
KrismithReddy12/claude-code-templates

planning-with-files

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

★ 0