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

evals/cases.yaml

View on GitHub
skill: gamedev-shipping

should_trigger:
  - prompt: "My Godot game runs in the editor but the exported web build just shows a black screen and the console says 'SharedArrayBuffer is not defined'. How do I host it?"
    why: "The signature web-ship failure: threaded WebAssembly needs COOP same-origin + COEP require-corp headers set at the host — core web-export-headers scope."
  - prompt: "How do I export and package my Unity 6 project as an AAB for the Google Play Store and sign it?"
    why: "Per-engine (Unity Build Profiles) + per-platform Android AAB vs APK + release keystore signing — squarely this skill's packaging boundary."
  - prompt: "I built my macOS game but users get a 'can't be opened because Apple cannot check it for malware' warning. What do I need to do before distributing it?"
    why: "macOS Gatekeeper rejection → the codesign (Hardened Runtime) + notarytool + stapler chain this skill owns."
  - prompt: "Set up a GitHub Actions workflow that headless-exports my Godot game for web and Linux on every tag and uploads the artifacts."
    why: "Headless-export CI/CD with matching export templates and version numbering — the CI section and stores-and-ci reference."
  - prompt: "I'm ready to publish to Steam. How do I upload my build with SteamPipe and push it to a beta branch first?"
    why: "Steamworks/SteamPipe VDF upload via steamcmd and branch promotion — store-prep scope."
  - prompt: "What's the difference between Development and Shipping when packaging my Unreal game, and which do I use for release?"
    why: "Unreal build-configuration choice for release packaging — per-engine export/build scope (Shipping vs Development)."
  - prompt: "Can I export my Godot C# project to the web? It keeps failing."
    why: "The known limitation: Godot's C#/.NET edition has no web export in 4.x — this skill must state that and route the user (GDScript or non-web target)."
  - prompt: "Push my HTML5 and Windows builds to itch.io with butler and bump the version."
    why: "itch.io butler channels + userversion, plus the SharedArrayBuffer support checkbox for web — store-prep scope."

should_not_trigger:
  - prompt: "Add double-jump and coyote-time to my player controller in Godot."
    route_to: "godot"
    why: "Gameplay/runtime code is the engine skill's job; this skill only packages and ships what the engine produces."
  - prompt: "Write a Dockerfile and Coolify config to deploy my Next.js web app with a Postgres database."
    route_to: "deployment"
    why: "Hosting a normal containerized web app/API is deployment's domain; a game ship is static WASM files or a native binary, not a container."
  - prompt: "My multiplayer game has rubber-banding; how do I add client-side prediction and server reconciliation?"
    route_to: "gamedev-multiplayer"
    why: "Netcode runtime behavior, not build/release — belongs to the multiplayer skill."
  - prompt: "Help me design the progression curve and reward economy for my roguelike."
    route_to: "game-design"
    why: "Game feel/economy design is not an export or packaging task."
  - prompt: "Optimize this fragment shader that's tanking my frame rate on mobile."
    route_to: "gamedev-shaders"
    why: "Runtime rendering performance is a shader-authoring concern, distinct from ship-time build-size/startup optimization."

capability:
  - scenario: "User's threaded Godot 4 web export fails with 'SharedArrayBuffer is not defined' and they plan to host it on Netlify (and later ask about GitHub Pages)."
    must_include:
      - "Explains threaded WASM needs cross-origin isolation via BOTH Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp response headers"
      - "Gives the Netlify _headers (or equivalent) config setting both headers, and notes itch.io's SharedArrayBuffer checkbox as an alternative"
      - "Notes GitHub Pages can't set headers, so use a single-threaded export or the coi-serviceworker shim"
      - "Mentions self.crossOriginIsolated === true as the verification check"
      - "Warns that Godot's C#/.NET edition has no web export in 4.x (only GDScript/standard)"
  - scenario: "User wants to ship a signed macOS desktop build for distribution outside the App Store."
    must_include:
      - "codesign with --options runtime (Hardened Runtime is mandatory for notarization) using a Developer ID Application identity"
      - "Submit with xcrun notarytool submit --wait (not the deprecated altool)"
      - "Staple the ticket with xcrun stapler staple so it verifies offline, and that skipping notarization means Gatekeeper blocks it"
  - scenario: "User asks how to produce and sign an Android release for Google Play from Unity."
    must_include:
      - "Requires JDK 17 and building an AAB (not APK) for Google Play"
      - "Generate/keep a release keystore (keytool) and never commit it; use Play App Signing"
      - "versionCode must strictly increase on every upload"
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