How do I install the Mobile Games skill?

Run npx skillmds@latest add techwavedev/mobile-games in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Mobile Games skill do?

Mobile game development principles. Touch input, battery, performance, app stores. It is listed under Coding & Dev Tools on SkillMD.

Is Mobile Games safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mobile Games?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mobile Games free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Mobile Games?

techwavedev (@techwavedev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mobile Games by techwavedev — Agent Skill

Name: Mobile Games
Rating: 4.5 (4 reviews)
Author: techwavedev

File contents

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.

AGI Framework Integration

Qdrant Memory Integration

Before executing complex tasks with this skill:

python3 execution/memory_manager.py auto --query "<task summary>"

Decision Tree:

Cache hit? Use cached response directly — no need to re-process.
Memory match? Inject context_chunks into your reasoning.
No match? Proceed normally, then store results:

python3 execution/memory_manager.py store \
  --content "Description of what was decided/solved" \
  --type decision \
  --tags mobile-games <relevant-tags>

Note: Storing automatically updates both Vector (Qdrant) and Keyword (BM25) indices.

Agent Team Collaboration

Strategy: This skill communicates via the shared memory system.
Orchestration: Invoked by orchestrator via intelligent routing.
Context Sharing: Always read previous agent outputs from memory before starting.

Local LLM Support

When available, use local Ollama models for embedding and lightweight inference:

Embeddings: nomic-embed-text via Qdrant memory system
Lightweight analysis: Local models reduce API costs for repetitive patterns

---name: mobile-gamesdescription: Mobile game development principles. Touch input, battery, performance, app stores.---# 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.## AGI Framework Integration### Qdrant Memory IntegrationBefore executing complex tasks with this skill:```bashpython3 execution/memory_manager.py auto --query "<task summary>"```**Decision Tree:**- **Cache hit?** Use cached response directly — no need to re-process.- **Memory match?** Inject `context_chunks` into your reasoning.- **No match?** Proceed normally, then store results:```bashpython3 execution/memory_manager.py store \ --content "Description of what was decided/solved" \ --type decision \ --tags mobile-games <relevant-tags>```> **Note:** Storing automatically updates both Vector (Qdrant) and Keyword (BM25) indices.### Agent Team Collaboration- **Strategy**: This skill communicates via the shared memory system.- **Orchestration**: Invoked by `orchestrator` via intelligent routing.- **Context Sharing**: Always read previous agent outputs from memory before starting.### Local LLM SupportWhen available, use local Ollama models for embedding and lightweight inference:- Embeddings: `nomic-embed-text` via Qdrant memory system- Lightweight analysis: Local models reduce API costs for repetitive patterns

Frequently asked questions

Mobile Games