Skills mobile-games
📦

mobile-games

Content revision r2 Safe

Design Better Mobile Games

Mobile games must balance touch usability, device limits, store rules, and business goals. This skill provides practical principles for making those decisions.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "mobile-games" from https://skillstore.io/skills/sickn33-mobile-games.md and its manifest at https://skillstore.io/api/skills/sickn33-mobile-games/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-mobile-games.md Signed manifest GET /api/skills/sickn33-mobile-games/manifest Signed lockfile GET /api/skills/sickn33-mobile-games/lockfile

Test it

Using "mobile-games". Review a portrait puzzle game with small tiles and time-sensitive swipes.

Expected outcome:

  • Increase interactive areas to at least 44 by 44 points.
  • Add immediate visual feedback for every swipe and selection.
  • Reduce precision and timing demands where mistakes block progress.
  • Test whether fingers hide important puzzle information.

Using "mobile-games". Suggest thermal responses for an action game targeting 60 frames per second.

Expected outcome:

  • When warm, reduce visual quality before changing gameplay.
  • When hot, lower the frame rate and expensive effects.
  • At critical temperature, pause nonessential effects and protect stability.
  • Measure each response on representative physical devices.

Using "mobile-games". Outline store preparation for a game with player accounts.

Expected outcome:

  • Prepare privacy labels and screenshots for required iOS device sizes.
  • Provide account deletion because the game supports account creation.
  • Target the current required Android API level.
  • Confirm 64-bit support and prepare an Android App Bundle.

Security Audit

Safe
v5 • 8/4/2026 Open versioned report

Both static findings are false positives caused by harmless mobile development guidance. No system reconnaissance, prompt injection, or other malicious intent appears in the reviewed skill.

1
Files scanned
119
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-mobile-games/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-mobile-games/security.svg)](https://skillstore.io/skills/sickn33-mobile-games?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-mobile-games?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-mobile-games/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-mobile-games.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). mobile-games security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-mobile-games/audits/5

BibTeX citation

@techreport{sickn33-sickn33-mobile-games-2026, author = {sickn33}, title = {mobile-games security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-mobile-games/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "mobile-games security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-mobile-games/audits/5" identifiers: - type: other value: "skillstore:sickn33-mobile-games:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
91
Spec Compliance

What You Can Build

Plan a Mobile Control Scheme

Review touch targets, gestures, screen occlusion, orientation, and feedback before implementation.

Set Device Performance Targets

Define frame rate, thermal throttling, pause behavior, and battery goals for a mobile build.

Prepare a Store Release

Create a checklist covering platform requirements, screenshots, privacy labels, packaging, and monetization choices.

Try These Prompts

Review Touch Controls 
Review my mobile game controls for touch usability, target size, feedback, screen occlusion, and orientation support.
Create Performance Targets 
Create performance, thermal, battery, pause, and network targets for my [genre] game on [supported devices].
Build a Release Checklist 
Build separate iOS and Android release checklists for my game, including store assets, privacy, account deletion, API level, and packaging.
Evaluate a Mobile Game Plan 
Evaluate this mobile game plan across controls, responsiveness, thermals, battery, interruptions, stores, monetization, and likely anti-patterns: [plan].

Best Practices

  • Test touch controls and performance on representative physical devices.
  • Define thermal and battery responses before final optimization.
  • Verify current store requirements shortly before every release.

Avoid

  • Do not reuse desktop controls without redesigning them for touch.
  • Do not ignore battery drain, thermal limits, or background interruptions.
  • Do not require continuous network access when caching and synchronization are sufficient.

Frequently Asked Questions

Which mobile platforms does this skill cover?
It covers general mobile constraints plus selected iOS App Store and Google Play requirements.
Does it provide Unity or Unreal code?
No. It provides platform and design principles that can guide implementation in any engine.
What touch target size does it recommend?
It recommends a minimum touch target of 44 by 44 points.
Does it help with battery and thermal performance?
Yes. It recommends frame rate, sleep, network, visual quality, and thermal response strategies.
Can it guarantee app store approval?
No. Store policies change, so teams must verify current official requirements before submission.
Does it recommend a monetization model?
It compares common models and their typical uses, but the final choice depends on the game and audience.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/game-development/mobile-games

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

9 downloads · 98 views

File structure

📄 SKILL.md

More from sickn33

View all

Related Skills

View all