What problem does it solve?
Developers adding the Gum UI framework to a C# game often struggle to understand how the editor, runtime libraries, and project files fit together, and frequently misconfigure content loading by using the MonoGame Content Pipeline instead of plain file copies.
Core Features & Use Cases
- Architecture Orientation: Explains the two visual layers (Forms controls vs raw visuals), the five XML project file types (.gumx, .gusx, .gucx, .gutx, .behx), and how states and categories work.
- Usage Mode Selection: Guides the choice between code-only UI, project loading with dynamic name lookup, and project loading with strongly-typed code generation.
- Correct Project Setup: Provides the GumService initialization pattern for MonoGame and the wildcard None copy rule that prevents runtime file-not-found failures.
- Use Case: A developer starting a new MonoGame project asks how to add Gum; the Skill explains which NuGet package to install, how to wire GumService into Initialize/Update/Draw, and how to configure content files so the .gumx project loads at runtime.
Quick Start
Ask how to add Gum to a MonoGame project and how to load a .gumx UI project at runtime.