Agent skill
publishing
Publishing Nethercore games to nethercore.systems. Covers ROM packaging with nether pack, release builds, platform upload requirements, versioning, and CI/CD pipeline setup with GitHub Actions. Use when preparing a game for release or setting up automated builds.
Install this agent skill to your Project
npx add-skill https://github.com/nethercore-systems/nethercore-ai-plugins/tree/main/nethercore/skills/publishing
Metadata
Additional technical details for this skill
- author
- nethercore-systems
- version
- 1.0.0
SKILL.md
Nethercore Publishing
Build Commands
| Command | Purpose |
|---|---|
nether build |
compile + pack (development) |
nether build --release |
Optimized release build |
nether pack |
Bundle WASM + assets into ROM |
Upload to nethercore.systems
Required:
| File | Format |
|---|---|
| Game | .wasm or .nczx |
| Icon | 64x64 PNG |
Optional:
- Screenshots (PNG, up to 5)
- Banner (1280x720 PNG)
Process:
- Create account at nethercore.systems
- Dashboard -> "Upload New Game"
- Fill metadata, upload files
- Publish
Pre-Release Checklist
-
nether build --releasesucceeds -
nether run --sync-testpasses - ROM under 16MB
- Icon is 64x64 PNG
- Description is compelling
- Version updated in nether.toml
Versioning
Semantic versioning in nether.toml:
[game]
version = "1.2.3"
Update process:
- Bump version in nether.toml
- Update CHANGELOG.md
- Commit, tag, push
- Re-upload to platform
CI/CD Quick Reference
| Gate | Command | Purpose |
|---|---|---|
| Format | cargo fmt --check |
Code style |
| Lint | cargo clippy -- -D warnings |
Static analysis |
| Test | cargo test |
Logic correctness |
| Build | nether build --release |
WASM compilation |
| Sync | nether run --sync-test --frames 1000 |
Determinism |
See references/ci-workflows.md for GitHub Actions templates.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
ffi-reference
ZX fantasy console FFI bindings reference. Documents 250+ functions for rendering, input, audio, camera, transforms, textures, materials, and debug. Includes init-only vs render-only call rules and the coordinate system. Use when writing or debugging ZX FFI calls in game code.
console-specs
ZX fantasy console hardware specifications and resource budgets. Covers resolution (960x540), memory limits (4 MB RAM/VRAM, 16 MB ROM), render modes, audio system (22 kHz, 16 channels), and input layout. Use when planning resource budgets or checking console capabilities.
rendering
ZX rendering techniques and patterns. Covers camera systems (follow, orbit), stencil buffer effects (portals, masks), billboard particles, custom fonts, and render pass management. Use when implementing cameras, visual effects, particle systems, or choosing between 2D and 3D rendering approaches.
debugging
Runtime debugging tools for Nethercore games on all consoles. Covers the F4 Debug Inspector, live value editing, watch variables, frame stepping, and time-scale controls. Use when tuning game parameters at runtime, tracking state over time, or stepping through frames to find bugs.
optimization
Optimization techniques for Nethercore WASM games. Covers WASM binary size reduction (LTO, wasm-opt), texture and mesh compression, audio optimization, and state size minimization. Use when a ROM exceeds size limits or when reducing build output size.
testing
Testing Nethercore games for determinism and correctness. Covers sync testing, replay recording and playback, debug actions, and desync diagnosis. Use when running sync tests, setting up replay-based regression tests, or diagnosing determinism failures.
Didn't find tool you were looking for?