MonoGame content pipeline
Makes models, textures, fonts and sounds reproducibly available in the built game. It distinguishes content-conversion problems from runtime lookup failures and gives shared content managers clear lifetimes.
monogame-content-pipeline
See how it helpsWhen is it useful?
Use when textures, fonts, models or audio fail between development and a packaged MonoGame build.
What does it help you do?
- Matches content tools and processors to the installed runtime and backend.
- Distinguishes build-time conversion failures from runtime lookup errors.
- Assigns shared content managers clear resource lifetimes.
Try asking this
Package our platformer with a sprite font, level textures and a custom effect. Build from a clean content output, then launch outside the IDE. Identify whether a missing asset failed conversion or lookup, and check scene changes do not unload content still needed by the menu.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
MonoGame — content pipeline
Use when importing MonoGame textures, models, fonts, audio or custom content processors.
Version and project gate
Inspect Project and .NET target, MonoGame package/backend, Game loop settings, MGCB files/tool versions, content root, GraphicsProfile, platform libraries and existing screen/state architecture. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Pin MGCB tool and runtime versions with the target backend/profile. Inventory source assets, processors and content names. Separate build-time content errors from runtime load paths. Preserve reproducible content output and give shared content managers explicit lifetime ownership.
Deliver
A content/build contract and a representative asset that loads from the packaged output. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
A file copied beside the executable is not necessarily Content.Load-compatible compiled content.
Acceptance scenario
Build from source assets in a clean output directory, omit one required asset and verify a useful load failure on the intended platform. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Mox. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
Included files 1
SKILL.md