Develop, fix, or review LÖVE 11.5 games hosted by Dora LoveNode, including Love TypeScript or Lua sources, Love API documentation lookup, isolated runtime boundaries, full-screen adaptation, filesystem behavior, and log-based debugging.
Dora SSR coding rules for game/workspace projects; prevents browser DOM/Canvas/Node.js code in Dora engine scripts and forces Dora API lookup before using unfamiliar engine APIs.
Use this skill when designing, creating, or polishing UI/screens/HUDs/menus so the result is visually refined, coherent, responsive, and implemented with the correct Dora UI APIs.
Rules and examples for using execute_command with Lua and Git safely inside the Dora Agent runtime.
Generate original game audio by authoring a typed exact score or procedural music definition, building it, and invoking the engine Async generator through execute_command.
Develop, test, benchmark, and iteratively validate Dora Agent changes with evidence from the current implementation, real `.agent` histories, controlled LLM trials, Dora in-engine tests, and human-visible acceptance. Use for changes to Agent prompts, tool…
Use when building, running, testing, or debugging Dora engine games with the Dora CLI, including TypeScript, TSX/DoraX, Lua, YueScript, Teal, XML, Wa, Yarn, Rust WASM, Web IDE service recovery, and in-engine validation.
Use when developing the Dora-SSR engine itself, including C++ engine code, Lua/YueScript dev services, generated bindings, DoraX runtime, Web IDE integration, docs, tests, local validation, and release-facing engine changes.