arch-packaging
Architecture reference for SGE game packaging targets and build configurations.
Install
mkdir -p .claude/skills/arch-packaging && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14722" && unzip -o skill.zip -d .claude/skills/arch-packaging && rm skill.zipInstalls to .claude/skills/arch-packaging
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Load the distribution packaging architecture for SGE games including JVM, browser, native, and Android targetsKey capabilities
- →Package SGE games for JVM targets
- →Create self-contained per-platform archives with jlinked JRE
- →Package SGE games for browser targets using Scala.js
- →Generate Scala Native executables with shared libraries
- →Build Android APKs via D8, aapt2, and apksigner
- →Manage cross-platform JVM distribution with native libraries
How it works
The skill describes the SGE game packaging architecture, detailing various modes for JVM, browser, native, and Android targets, and how native libraries are integrated for cross-platform distribution.
Inputs & outputs
When to use arch-packaging
- →Configuring game packaging builds
- →Reviewing SGE platform build architecture
- →Managing cross-platform game releases
About this skill
Distribution packaging architecture for SGE games.
Key Files
sge-build/src/main/scala/sge/sbt/SgePackaging.scala— Core packaging logicsge-build/src/main/scala/sge/sbt/SgePlugins.scala— SgeDesktopJvmPlatform, SgeBrowserPlatform, SgeDesktopNativePlatform, SgeAndroidPlatformdemos/build.sbt— Demo packaging configuration
Packaging Modes
- Simple (
sgePackage): bin/ + lib/ + native/ with launcher scripts, requires system JDK - Distribution (
sgePackageAll): Self-contained per-platform archives with jlinked JRE + Roast launcher - Browser (
sgePackageBrowser): Scala.js fullLinkJS + index.html + assets - Native (
sgePackageNative): Scala Native executable + shared libs - Android (
androidSign): APK via D8 + aapt2 + apksigner
Cross-Platform JVM Distribution
sgeCrossNativeLibDirsetting: points tosge-deps/native-components/target/cross/(CI staging area)- Native libs built externally in sge-native-providers, distributed as provider JARs
- CI extracts provider JARs to the staging dir; per-platform libs in
cross/<classifier>/ - ANGLE libs (libEGL, libGLESv2) bundled alongside Rust libs
- Static curl libs (from stunnel/static-curl) for self-contained Scala Native releases
- macOS .app bundles with ad-hoc codesigning
Release Workflow
Native libs are built externally in
sge-native-providers and
distributed as provider JARs from Maven. The release flow consumes those
provider JARs and builds the per-platform demo archives via sbt
command aliases defined in demos/build.sbt.
re-scale build publish-local --all # Publish SGE to local Maven (JVM + JS + Native)
re-scale runner release-build # sbt --client releaseAll (in demos/)
re-scale runner release-collect # sbt --client collectReleases — demos/target/releases/
re-scale runner android-build-all # sbt --client androidAll — all 11 demo APKs
Per-demo (single demo) is wired via sbt command aliases inside demos/,
e.g. cd demos && sbt --client releasePong for the JVM/Browser/Native trio
of the Pong demo, or sbt --client androidPong for the APK alone.
Verification
Manual archive launch / smoke verification was previously done by legacy shell wrappers that are no longer present. There are no equivalent sbt tasks yet — verify by running the integration test runners on the host platform:
re-scale runner desktop-it # GLFW + ANGLE + miniaudio integration test
re-scale runner browser-it # Playwright + headless Chromium
re-scale runner android-it # Android emulator smoke test
re-scale runner native-ffi-it # Scala Native C ABI wiring
Load the SgePackaging source for implementation details: $READ sge-build/src/main/scala/sge/sbt/SgePackaging.scala
When not to use it
- →When the project is not an SGE game
- →When only a single platform target is needed without cross-platform considerations
- →When the user does not want to use sbt for packaging
Limitations
- →Requires external native libraries built in `sge-native-providers`
- →Manual archive launch / smoke verification is required as no sbt tasks exist yet
- →macOS .app bundles use ad-hoc codesigning
How it compares
This skill provides a specialized packaging architecture for SGE games, covering multiple platforms (JVM, browser, native, Android) with specific tools and workflows, unlike general software packaging solutions.
Compared to similar skills
arch-packaging side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| arch-packaging (this skill) | 0 | 3mo | Review | Advanced |
| gcp-cloud-run | 5 | 5mo | Review | Intermediate |
| deployment-pipeline-design | 6 | 2mo | Review | Advanced |
| cloudflare-deploy | 3 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
gcp-cloud-run
aj-geddes
Deploy containerized applications on Google Cloud Run with automatic scaling, traffic management, and service mesh integration. Use for container-based serverless computing.
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
cloudflare-deploy
davila7
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
monorepo-architect
sickn33
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup,
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.