Engine Guide gives an agent one guide per engine: Godot 4 with C# or GDScript, Bevy in Rust, Babylon.js, three.js and an HTML and canvas stack. Each covers the project sketch, build commands, headless capture to screenshots and video, and the traps that pass a build but fail at runtime.
It also helps choose between engines by what you will hold at the end and how you want to watch progress. Because capture steps a fixed timestep per frame, the same guides cover videos, trailers, explainers and interactive pages made in an engine.
What You Get
- A guide per engine: godot.md, godot-gdscript.md, bevy.md, babylon.md, threejs.md and html.md
- A setup guide for installing ffmpeg, ImageMagick, Godot with .NET, Rust, Node and headless-browser tooling at current versions
- Build gates and capture recipes that turn a scene into screenshots or an encoded video
- A list of silent-failure traps for each engine, such as dropped nodes in a saved Godot scene or macOS hangs on fatal errors
- Guidance for using an engine as a video studio with voice-over and music on one timeline
Common Use Cases
- Start a game and pick the engine that fits how you want to follow progress
- Make a trailer, explainer or product showcase as an engine-rendered video
- Build an interactive 3D landing scene or data visualization in three.js or Babylon.js
- Capture screenshots from a headless Godot or Bevy project
- Continue work on an existing engine project with its traps in mind
What Makes It Unique
The guides skip what a model already knows and keep the failures that give no error: Godot scenes that save without some nodes, shadows that vanish without generated normals, and a macOS fatal error that hangs a headless run. Capture uses a fixed timestep, so render cost never shows in the output, which lets the same tools produce deterministic video. Engine choice is treated as the user’s call because switching later means a rewrite.
Under The Hood
The skill is reference text: SKILL.md plus one guide per engine and a setup file, with no scripts of its own. The instructions tell the agent to run shell commands: check installed versions, install toolchains and system packages, download Godot releases from GitHub, run dotnet, cargo, npm and Vite builds, start headless Godot under a timeout, render with xvfb, and encode video with ffmpeg. That means it downloads software, writes project files and captured frames into your project, and needs a hardware GPU path for video capture. It says to give you the one command to run when a step needs root.