Skip to content

ericrisco/rsc-harness / skills/gamedev-shipping

gamedev-shipping

Verified

Use when exporting, packaging, signing, or publishing a game — export presets per engine, macOS notarization, cross-origin isolation for threaded web builds, Android AAB/keystore, iOS provisioning, store submission (Steam, Play, App Store, itch.io), headless build CI. NOT gameplay code inside the artifact (that is `godot`, `unity`, `unreal`), NOT hosting a web app or container (that is `deployment`).

FileKindSize
SKILL.mdskill md13.8 KB
evals/README.mdmarkdown627 B
evals/cases.yamlconfig4.8 KB
references/mobile-and-desktop.mdmarkdown6.5 KB
references/stores-and-ci.mdmarkdown6.5 KB
references/web-export-headers.mdmarkdown6.3 KB

references/mobile-and-desktop.md

View on GitHub
# Mobile & desktop — signing, keystores, provisioning, notarization

Back to the entrypoint: `../SKILL.md`. The per-OS steps that gate a shippable build.

## Android

### Toolchain

- **JDK 17** — the version the current Gradle build template expects. JDK 21 or 11 breaks the
  build with cryptic Gradle errors. Point the engine's Android settings at a JDK 17 home.
- **Android SDK + build-tools + platform-tools**; NDK for native/IL2CPP.
- Godot: `Project ▸ Install Android Build Template`, then tick **Use Gradle Build** on the Android
  preset — required to produce an **AAB** and to use custom Gradle/plugins.
- Unity: `File ▸ Build Profiles ▸ Android`; **Build App Bundle (Google Play)** for AAB.
- Unreal: run **Turnkey**/Android setup once (Android Studio + correct NDK), then
  `RunUAT BuildCookRun ... -platform=Android -clientconfig=Shipping -distribution -cook -stage -pak -package`.

### AAB vs APK

| Format | Use for | Notes |
| --- | --- | --- |
| **AAB** (`.aab`) | Google Play (**required** for new apps + updates) | Play generates optimized per-device APKs; you can't install an AAB directly. |
| **APK** (`.apk`) | Sideload, itch.io, direct download, other stores | Installs directly; use a universal APK for QA. |

### Signing & keystore

Generate a release keystore **once** and guard it — losing it means you can't publish updates
(unless enrolled in Play App Signing, where Google holds the app-signing key and you rotate the
upload key):

```bash
keytool -genkey -v -keystore release.keystore -alias game \
  -keyalg RSA -keysize 2048 -validity 10000
```

- Godot: set the **Release** keystore path + alias + passwords in the Android preset (and a debug
  keystore for debug exports).
- Never commit the keystore or passwords. In CI, restore the keystore from a base64-encoded secret
  at runtime and pass passwords via env.
- **Play App Signing**: you sign the upload with the *upload key*; Google re-signs distribution
  with the *app-signing key* it stores. Recommended — it lets you recover a lost upload key.
- `versionCode` (integer) must **strictly increase** every upload; `versionName` is the human string.

### Common failures

- Editor 4.5.1 + templates 4.5 ⇒ export greyed out or Gradle error. Match versions exactly.
- Wrong JDK ⇒ Gradle build fails. Use 17.
- Debug keystore used for a release ⇒ Play rejects it.
- Target API level too old ⇒ Play blocks the submission.

## iOS

- **Mac + Xcode + an Apple Developer Program membership** (paid) are non-negotiable for device/store builds.
- **Bundle Identifier** must match a registered **App ID** in the developer portal.
- **Signing certificate** (Apple Development / Apple Distribution) + a **provisioning profile**
  that ties App ID + certificate + devices/distribution method:
  - *Development* — run on registered test devices.
  - *Ad Hoc* — distribute to a fixed device list outside the store.
  - *App Store* — submit to App Store Connect / TestFlight.
- Enable **Automatically manage signing** in Xcode for the common case; use manual profiles for CI.
- Flow: engine exports an Xcode project → open in Xcode → set team/signing → **Product ▸ Archive**
  → distribute via the Organizer, or upload with **Transporter** to App Store Connect.
- **TestFlight** for beta: upload a build, add internal/external testers, then submit for review.
- `CFBundleShortVersionString` = marketing version; `CFBundleVersion` = build number, must
  **increase** per upload to App Store Connect.

## macOS (desktop, outside the App Store)

Gatekeeper will refuse an unsigned/un-notarized app for end users. The full chain is codesign →
notarize → staple, inside-out.

```bash
# 1. Sign every nested binary FIRST, then the outer .app (Hardened Runtime is mandatory)
codesign --deep --force --timestamp --options runtime \
  --sign "Developer ID Application: Studio Name (TEAMID)" Game.app

# 2. Store notarization creds once (App Store Connect API key or Apple ID app-password)
xcrun notarytool store-credentials "AC" \
  --apple-id you@studio.com --team-id TEAMID --password app-specific-pw

# 3. Zip and submit; --wait blocks until Apple returns accepted/invalid
ditto -c -k --keepParent Game.app Game.zip
xcrun notarytool submit Game.zip --keychain-profile "AC" --wait

# 4. Staple the ticket so the app verifies OFFLINE, then verify
xcrun stapler staple Game.app
spctl --assess --type execute -vvv Game.app   # should say: accepted, source=Notarized Developer ID
```

- `--options runtime` (Hardened Runtime) is **required** or notarization is rejected.
- Sign nested `.dylib`s / helper tools / frameworks before the parent bundle.
- Distributing a `.dmg`? Notarize and staple the **`.dmg`** too (submit the dmg, staple the dmg).
- `altool` notarization is retired — use `xcrun notarytool`.
- If `notarytool` returns `Invalid`, fetch the log: `xcrun notarytool log <submission-id> --keychain-profile "AC"`.

### Mac App Store (different path)

- Sign with **Apple Distribution** (not Developer ID) + **App Sandbox** entitlements.
- Submit through App Store Connect (via Xcode/Transporter); the store notarizes automatically —
  you do not run `notarytool`/`stapler` manually for App Store builds.

## Windows

- Signing is **optional** but recommended: an Authenticode code-signing certificate reduces the
  SmartScreen "unknown publisher" warning. An **EV** certificate builds reputation faster.

```powershell
signtool sign /fd SHA256 /tr http://timestamp.digicert.com /td SHA256 /a Game.exe
```

- Ship the `.exe` alongside the engine data/`.pck` (or bundle into an installer: Inno Setup / NSIS / MSIX).
- Unsigned still runs; users just click through a SmartScreen prompt.

## Linux

- No signing requirement. Ship the executable + data files, or wrap for portability:
  - **AppImage** — one self-contained file, runs across distros; easiest for direct/itch distribution.
  - **Flatpak** — sandboxed, distributed via Flathub; more packaging work, best store reach.
- Mark the binary executable (`chmod +x`) and test on a clean distro (glibc version differences bite).

## Cross-platform checklist

- [ ] Android: JDK 17, AAB for Play (APK for sideload), release keystore in CI secret, `versionCode` bumped, Play App Signing on.
- [ ] iOS: App ID + cert + provisioning profile matched, `CFBundleVersion` bumped, archive uploaded.
- [ ] macOS: codesign (Hardened Runtime) → notarytool → stapler → `spctl` accepted.
- [ ] Windows: signed (or SmartScreen prompt accepted as known), installer built if needed.
- [ ] Linux: AppImage/Flatpak or binary+data, tested on a clean distro.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall