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/stores-and-ci.md

View on GitHub
# Stores & CI — Steam, itch.io, Play/App Store, and headless build pipelines

Back to the entrypoint: `../SKILL.md`. Store submission mechanics and per-engine CI.

## Steam (Steamworks + SteamPipe)

1. **Partner setup**: Steamworks account, an **App ID**, and the store page (assets, description,
   trailers, tags, pricing) filled in the partner site.
2. **Depots**: a depot is a bucket of files for a platform/language (e.g. one Windows depot, one
   macOS depot). Map each to your App ID.
3. **SteamPipe upload** with `steamcmd` driven by VDF scripts.

`app_build_APPID.vdf`:

```
"appbuild"
{
  "appid" "480"
  "desc"  "1.2.3 - CI build"
  "buildoutput" "output/"
  "contentroot" "build/"
  "setlive" ""                      // leave empty; set a branch live in the site, or "beta"
  "depots" { "481" "depot_build_481.vdf" }
}
```

`depot_build_481.vdf`:

```
"DepotBuild"
{
  "DepotID" "481"
  "FileMapping" { "LocalPath" "*" "DepotPath" "." "recursive" "1" }
  "FileExclusion" "*.pdb"
}
```

Upload:

```bash
steamcmd +login <builder_account> +run_app_build $(pwd)/app_build_APPID.vdf +quit
```

- Push to a **beta branch** first, test, then set it as the default (live) branch in the partner site.
- Use a dedicated **build account** with 2FA handled for CI (Steam Guard); never the studio owner login.
- `.pdb`/debug symbols usually excluded from the shipped depot.

## itch.io (butler)

`butler` is itch's CLI. A **channel** encodes the platform:

```bash
butler push build/windows user/game:windows   --userversion 1.2.3
butler push build/html5   user/game:html5      --userversion 1.2.3
butler push build/osx.zip user/game:mac        --userversion 1.2.3
butler status user/game                        # see channels + versions
```

- Channel names containing `windows`/`osx`/`linux`/`android` tag the platform for the itch app;
  `html5`/`web` marks a browser build.
- For threaded web builds, in the uploaded file's settings tick **"This file will be played in
  the browser" ▸ SharedArrayBuffer support** so itch serves COOP/COEP (see `web-export-headers.md`).
- CI auth: `BUTLER_API_KEY` env var (from itch API keys). `butler push` is idempotent and diff-based.

## Google Play

- Upload an **AAB**; enable **Play App Signing**.
- Meet the current **target API level** requirement (Play enforces a recent level for new uploads and updates).
- Complete: **content rating** (IARC questionnaire), **Data safety** form, store listing (icon,
  feature graphic, screenshots per device, short/full description), pricing/countries.
- Tracks: internal → closed → open → production. Promote a build up the tracks.
- `versionCode` strictly increasing; can't reuse one.

## Apple App Store

- Archive + upload to **App Store Connect** (Xcode Organizer / Transporter).
- App Store record: name, subtitle, keywords, description, screenshots per device size, app icon,
  privacy nutrition labels, **age rating** questionnaire, pricing.
- **TestFlight** for beta before submitting for review.
- The store notarizes automatically — no manual `notarytool` for App Store builds.

## Age ratings (shared)

- **IARC** questionnaire generates ratings for Google Play, Microsoft Store, Nintendo eShop in one pass.
- **ESRB** (NA), **PEGI** (EU), **USK** (DE), **CERO** (JP) as required by platform/region.
- Apple has its own age-rating questionnaire in App Store Connect.
- Answer truthfully — misdeclaring content (violence, gambling, user-generated content) risks removal.

## CI/CD — headless builds

Principles: run the export headless, feed a **version/build number** from the CI run, restore
**signing material from secrets** at runtime, upload the artifact.

### Godot (GitHub Actions)

```yaml
name: export
on: { push: { tags: ['v*'] } }
jobs:
  build:
    runs-on: ubuntu-latest
    container: barichello/godot-ci:4.5.1        # image bundles matching export templates
    steps:
      - uses: actions/checkout@v4
      - name: Prepare templates
        run: |
          mkdir -p ~/.local/share/godot/export_templates/4.5.1.stable
          mv /root/.local/share/godot/export_templates/4.5.1.stable/* \
             ~/.local/share/godot/export_templates/4.5.1.stable/
      - name: Export Web + Linux
        run: |
          mkdir -p build/web build/linux
          godot --headless --export-release "Web"   build/web/index.html
          godot --headless --export-release "Linux/X11" build/linux/game.x86_64
      - uses: actions/upload-artifact@v4
        with: { name: builds, path: build/ }
```

The template version in the image **must** equal the editor build (`4.5.1` here). For Android in CI,
add JDK 17 + the Android SDK and restore the keystore from a secret.

### Unity (GitHub Actions)

```yaml
- uses: game-ci/unity-builder@v4
  with:
    targetPlatform: Android
    buildMethod: BuildScript.PerformBuild
  env:
    UNITY_LICENSE: ${{ secrets.UNITY_LICENSE }}
    UNITY_EMAIL:   ${{ secrets.UNITY_EMAIL }}
    UNITY_PASSWORD: ${{ secrets.UNITY_PASSWORD }}
```

- License activation is required (personal/pro); store it in secrets via `game-ci/activate`.
- Matrix over `targetPlatform` for multi-target. Keystore + passwords come from secrets for signed Android.

### Unreal (self-hosted)

- The engine install is multi-GB, so Unreal CI needs a **self-hosted runner** with the engine + SDKs installed.
- Drive with `RunUAT BuildCookRun ... -clientconfig=Shipping -cook -stage -pak -package -archivedirectory=...`.

### Versioning

```yaml
env:
  BUILD_NUMBER: ${{ github.run_number }}          # monotonic → versionCode / CFBundleVersion / Steam desc
  VERSION: ${{ github.ref_name }}                  # semver tag → versionName / marketing version
```

- Semver tag (`v1.2.3`) triggers a release build; the run number is the strictly-increasing integer.
- Feed `BUILD_NUMBER` into Android `versionCode`, iOS `CFBundleVersion`, and the Steam build `desc`.
- Publish signing secrets (keystore base64, App Store Connect API key, `BUTLER_API_KEY`, `STEAM_*`) as encrypted repo/environment secrets — never in the workflow file.

## Checklist

- [ ] Store page assets + metadata + age rating complete for the target store.
- [ ] Steam: depots mapped, SteamPipe VDFs correct, pushed to a beta branch first, build account with Steam Guard.
- [ ] itch: correct channel names, SAB checkbox for web, `BUTLER_API_KEY` in CI.
- [ ] Play: AAB + Play App Signing + target API level + Data safety.
- [ ] App Store: archive uploaded, TestFlight tested, privacy labels + age rating done.
- [ ] CI: headless export, version/build number from the run, signing material from secrets, artifact uploaded.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated 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