Use when delivering a game on iOS, iPadOS, or macOS with Apple-native services, Metal diagnostics, controllers, haptics, cloud saves, signing, notarisation, sandboxing, or Mac window and display behaviour.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add peterbamuhigire/chwezi-dev-engine --skill apple-game-platform-delivery --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Apple Game Platform Delivery?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/peterbamuhigire-apple-game-platform-delivery)More formats (shields.io, HTML) on the badges page.
---
name: apple-game-platform-delivery
description: Use when delivering a game on iOS, iPadOS, or macOS with Apple-native services, Metal diagnostics, controllers, haptics, cloud saves, signing, notarisation, sandboxing, or Mac window and display behaviour.
metadata: {portable: true, compatible_with: [claude-code, codex]}
---
# Apple Game Platform Delivery
Own the Apple-specific boundary between a game engine or SpriteKit project and a tested, distributable iPhone, iPad, or Mac game.
## Use When
- Integrating Apple game services or diagnosing Apple-only runtime, input, graphics, save, signing, or distribution failures.
- Choosing Mac App Store, direct notarised distribution, or another approved storefront.
## Do Not Use When
- The task is general iOS application work; use the iOS family.
- Current Apple requirements and the pinned Xcode/OS/engine versions cannot be verified.
## Required Inputs
Game/engine version, Xcode version, target OS and hardware matrix, distribution channel, bundle identifiers, entitlements, service/data map, signing ownership, save model, input/display requirements, and acceptance criteria.
## Workflow
1. Pin the toolchain and verify current Apple requirements from official sources.
2. Define platform adapters for identity, Game Center, controllers, haptics, cloud saves, purchases, lifecycle, and diagnostics; keep gameplay independent.
3. Specify Mac windowed/full-screen behaviour, Retina scaling, multi-display changes, keyboard/mouse/controller remapping, focus loss, and safe save locations.
4. Test Metal-relevant failures on representative Apple hardware and retain captures with build, device, OS, scene, and conditions.
5. Rehearse certificate/provisioning failure, entitlement mismatch, offline service failure, save conflict, suspend/terminate, and controller disconnect.
6. Archive once, retain symbols/checksums, and promote the tested artefact through signing, hardened-runtime, sandbox, notarisation, and channel gates as applicable.
## Quality Standards
- Never transplant obsolete Swift, SpriteKit, Game Center, or Xcode APIs from a book; preserve only the architectural lesson and verify the current API.
- Apple services degrade without corrupting local state or blocking offline-capable play.
- No signing key or service secret enters the client repository.
## Outputs
Apple platform contract; service adapters; device/display/input matrix; entitlement and signing register; tested archive with symbols/checksum; distribution and rollback record.
## References
- [Apple game delivery gates](references/apple-game-delivery-gates.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!