Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
A structured workflow for building HTML5 games using Rust+WASM (Macroquad or Bevy) or Godot 4.x. JavaScript and TypeScript frameworks are explicitly prohibited. The pipeline follows an asset-first approach with TDD and Playwright-based QA automation before deployment.
Enforcing Rust+WASM or Godot over JS frameworks avoids runtime fragility and keeps WASM bundle sizes and toolchain choices predictable across the full asset-to-deployment pipeline.
When to use it
- Building a new browser game with Rust and Macroquad
- Exporting a Godot 4 project to HTML5 for web deployment
- Writing test cases before implementing game mechanics
- Running automated QA checks on a game with Playwright
- Acquiring and validating free-license assets before starting development
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Create a Snake game that runs in the browser
- 1Acquire sprite, background, BGM, and SFX assets from kenney.nl or NAS before writing any code
- 2Write functional, UI, and performance test cases covering game loop, mobile viewport, and load time
- 3Initialize a Macroquad project and implement snake movement, collision, and scoring logic
- 4Run Playwright automated tests against the local build to verify all TCs pass
- 5Build the WASM release and deploy index.html and .wasm to the target web server
Deployed HTML5 Snake game passing all test cases, with 4 screenshots and a completed Definition of Done checklist
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.