game-dev-rust-godot
Game development workflow using Rust+WASM or Godot 4.x for HTML5 games. Use when creating new games, implementing game mechanics, or porting existing games. Follows TDD-based production pipeline v3.1 with asset-first approach. Covers Rust(Macroquad/Bevy), Godot HTML5 Export, asset acquisition, test case writing, and QA automation. Master directive (2026-02-06) - ONLY Rust+WASM or Godot allowed, JS/TS frameworks prohibited.
Why use this skill?
Build lightweight HTML5 games using Rust/WASM or Godot 4.x. Follow our TDD-based production pipeline for optimal performance and asset-first development.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/kjaylee/game-dev-rust-godotWhat This Skill Does
The game-dev-rust-godot skill provides an end-to-end framework for developing high-performance HTML5 games using Rust (with Macroquad or Bevy) or Godot 4.x. It enforces a strict, disciplined workflow (TDD-based production pipeline v3.1) that mandates asset acquisition before coding. By prohibiting JavaScript/TypeScript frameworks, the skill ensures all generated projects are lightweight, efficient, and optimized for WASM, adhering to the 2026-02-06 master directive for game development.
Installation
You can install this skill directly via the ClawHub command line interface. Simply run the following command in your terminal:
clawhub install openclaw/skills/skills/kjaylee/game-dev-rust-godot
Once installed, the skill will integrate into your OpenClaw environment, providing specialized commands for project scaffolding, asset pipeline management, and testing.
Use Cases
- Creating New Games: Ideal for developers looking to start a new web-based project from scratch using high-performance technologies.
- Game Mechanics Implementation: Use the skill to iterate on specific game logic, utilizing TDD to ensure stability and correctness before full implementation.
- Porting: Effortlessly migrate existing game logic into a compliant Rust/WASM or Godot-based HTML5 format.
- QA Automation: Automate UI/UX verification using the integrated Playwright and manual test case protocols defined in the pipeline.
Example Prompts
- "Initialize a new Macroquad project named 'gravity-jump' and create a skeleton structure for an infinite runner game."
- "I have collected the assets for my platformer; please generate a list of TDD test cases for the jump physics and collision detection systems."
- "Convert this Godot 4.x scene into an optimized HTML5 export structure, ensuring all project settings meet the TDD v3.1 requirements."
Tips & Limitations
- Asset Priority: You must follow the asset acquisition pipeline. Never begin coding without first validating your asset library.
- Technology Restrictions: Remember that JS/TS frameworks (like Phaser or Three.js) are strictly prohibited. Always lean on Macroquad for lightweight projects or Bevy for complex ECS needs.
- Performance: For browser-based games, prioritize Macroquad to keep WASM binary sizes small. Bevy is powerful but carries a heavy compilation cost and larger footprint.
- TDD Requirement: Ensure that all functional and UI/UX test cases are written before you write your implementation code. This is a non-negotiable step in our quality assurance pipeline.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-kjaylee-game-dev-rust-godot": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution
Related Skills
ui-ux-pro-max
UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.
ralph-loop
AI 자율 구현 방법론. 구현/개발/코딩 요청 시 자동 적용. 메인은 마더 서브에이전트를 spawn하고, 마더가 워커들을 관리. specs/ → IMPLEMENTATION_PLAN.md → 1태스크씩 구현 → 2단계 리뷰 → 테스트 → 반복.
subagent-dev
Execute implementation plans using fresh subagents per task with two-stage review (spec compliance + code quality). Use when executing multi-task plans with independent work units. Enhances ralph-loop methodology.
stripe-payments
Best practices for Stripe payment integration. Use when implementing payments, subscriptions, checkout flows, or any monetization feature in games or web apps. Covers CheckoutSessions, Payment Element, subscriptions, and Connect.
systematic-debugging
Root-cause-first debugging methodology. Use when encountering any bug, test failure, or unexpected behavior BEFORE proposing fixes. Prevents random fix attempts that waste time and create new bugs.