Ebitengine Game is a delivery workflow for 2D games written in Go with Ebitengine v2. It bundles a starter project, a read-only API checker and a macOS app packager, and walks the agent from a short brief through a playable slice to a verified, buildable game.
It covers the Update, Draw and Layout contracts, input actions, rendering and pixel-art sampling, text, audio, tests and screenshots, and the common failures: missed key presses, blurry pixel art, speed that follows the monitor and audio panics.
What You Get
- A starter platformer generated by new_game.py with scenes, action input, text, sound, camera, pause and scripted capture
- A read-only checker, check_ebitengine.py, that flags deprecated APIs, ReadPixels use and work done in Draw
- A macOS app packager that builds a universal .app from built binaries
- Reference files on rendering, input, text and UI, audio, assets, playtest diagnostics, architecture, tilemaps, networking and publishing
- A verification routine with go vet, go test, the checker, a build and a screenshot capture
- A gotchas list that maps symptoms to causes and fixes
Common Use Cases
- Starting a new 2D game in Go and getting to a playable slice
- Fixing blurry pixel art, missed key presses or stutter in an existing Ebitengine game
- Producing desktop, WASM or macOS builds and a release checklist
- Reviewing old Ebitengine code for deprecated API use
What Makes It Unique
Most engine skills explain an API. This one defines done as a complete, playable loop and ties the workflow to checks: a bundled checker, a test run, rendered screenshots paired with game state, and builds for every promised target. It also states what a scripted run cannot judge, such as control feel and sound, and hands those to the user.
Under The Hood
The skill is a SKILL.md with a starter project, three Python scripts and many reference files. The agent runs the scripts, which copy the starter into a new folder, scan Go source read-only, or assemble a macOS app bundle with lipo. It also runs the Go toolchain: go mod tidy fetches dependencies from the network, then go vet, go test and go build, including cross-compiles. On Linux it may start a virtual display and write a temporary audio config file to capture a screenshot. Optional CI setup writes a GitHub Actions workflow into the project. Publishing and uploads are left to you. The Go source files of the bundled starter were not scanned by the server, so read them before running the starter.