mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
- License 许可
- MIT
- 最近更新
- 2026-05-10
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- mobile-games
- description
- Mobile game development principles. Touch input, battery, performance, app stores.
- allowed-tools
- Read, Write, Edit, Glob, Grep
02 资源文件 1
- 参考文档.skill-source.json307 B
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
zustand-store-ts
Create Zustand stores following established patterns with proper TypeScript types and middleware.
zod-validation-expert
Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.
zinc-database
Access ZINC (230M+ purchasable compounds). Search by ZINC ID/SMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.
zarr-python
Chunked N-D arrays for cloud storage. Compressed arrays, parallel I/O, S3/GCS integration, NumPy/Dask/Xarray compatible, for large-scale scientific computing pipelines.
zapier-workflows
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
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