xnafiddle

Creates XNA-syntax fiddles that run in browsers and export to MonoGame, KNI, or FNA runtimes.

614|78|Updated Mar 11, 2015
One-click install
npx skills add https://github.com/vchelaru/Gum --skill xnafiddle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xnafiddle
Source: https://github.com/vchelaru/Gum/tree/main/.claude/skills/xnafiddle
Command: npx skills add https://github.com/vchelaru/Gum --skill xnafiddle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing engine-level behavior across XNA-compatible runtimes normally requires setting up multiple local projects per backend and platform. XnaFiddle lets you author a small XNA-syntax project in the browser, run it immediately, and export it to a chosen runtime and platform — even linking against engine source instead of NuGet packages.

Core Features & Use Cases

  • Cross-backend web fiddles: Write XNA-syntax code that compiles and runs directly in the browser without local project setup.
  • Source-linked engine export: Export to MonoGame, KNI, or FNA targeting platforms like desktop, web, or Android, optionally linking engine source (emitting one .slnx with per-platform projects) so you can toggle engine build constants and prove engine-side behavior.
  • Shareable upstream repros: Create public repros for KNI/MonoGame/FNA engine issues that maintainers can run in a couple of clicks.
  • Gum and third-party library support: Fiddles are Gum-aware, and ILibraryPlugin implementations (e.g. KernSmithPlugin) auto-detect referenced libraries via IsUsedInSource and pull in the right NuGet packages at export.
  • Use Case: You suspect a KNI rendering bug only appears with a specific build constant. Create a fiddle, export it source-linked to KNI for desktop, toggle the constant, and confirm the engine-side behavior — then share the public fiddle link with the KNI maintainers.

Quick Start

Ask the assistant to create an XnaFiddle that reproduces your engine behavior and export it source-linked to your chosen runtime and platform.

Frequently Asked Questions about xnafiddle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a cross-platform XNA repro that runs in the browser?

Author a fiddle in XNA syntax on XnaFiddle, which compiles and runs directly in the browser. On export you choose the target runtime (MonoGame, KNI, or FNA) and platforms such as desktop, web, or Android.

How to test MonoGame or KNI engine source instead of the NuGet package?

XnaFiddle export can link against engine source rather than the shipped NuGet package, emitting one .slnx with per-platform projects. This lets you toggle engine build constants and prove engine-side behavior directly.

When should I use XnaFiddle instead of the local Gum Samples projects?

Use the local Samples projects when testing whether Gum consumes the shipped engine correctly, since they link the Gum runtime from source with the engine via NuGet. Use XnaFiddle when you need a self-contained engine-source experiment or a public repro for an upstream engine issue.

Can XnaFiddle fiddles use Gum or third-party libraries?

Yes, fiddles are Gum-aware and referencing a third-party library in fiddle source is enough to pull it in at export. Each ILibraryPlugin, such as KernSmithPlugin, auto-detects usage via IsUsedInSource and adds the right NuGet packages.

What if XnaFiddle has no plugin for the library I need?

If no ILibraryPlugin exists yet for a library, request one rather than ruling the fiddle out. XnaFiddle is maintained by Victor, so it is feature-requestable rather than a fixed third-party black box.