What problem does it solve? Setting up the resonite-io development environment on a fresh clone involves many failure-prone steps: Docker/devcontainer configuration, GPU vendor detection, Gale mod profile creation, Wine DLL overrides, and AppArmor restrictions. This Skill consolidates the full checklist and explains the common pitfalls so mod-load failures can be diagnosed quickly. ## Core Features & Use Cases - Docker devcontainer setup: Guides just init, .env configuration with ResonitePath, and opening the devcontainer via VS Code, Zed, or @devcontainers/cli, with all .NET/uv/protoc tooling containerized. - Gale profile management: Explains creating a Gale profile at ./gale, importing the bundled GaleProfile.r2z snapshot or manually installing the six required mods, and validating with just check-gale. - Launch and troubleshooting: Covers WINEDLLOVERRIDES="winhttp=n,b" requirements for Steam Launch Options vs container auto-export, AppArmor kernel.apparmor_restrict_unprivileged_userns=0, UDS path constraints under pressure-vessel, and the just resonite-launch / just resonite-stop mod-load verification flow. - Use Case: After a fresh clone, run just init, open the devcontainer, deploy the mod with just deploy-mod, launch Resonite with just resonite-launch, and confirm Loading Plugin ResoniteIO appears in the BepInEx log. ## Quick Start Set up my resonite-io dev environment from this fresh clone, including the Gale profile and Steam launch options.