- Tool
- REA
- Provider or project
- JoasASantos community collection
- Source type
- Community-authored
Who should use it
Game developers evaluating a browser port of a project they own.
Practical uses
- Check whether the rules for an original puzzle game can compile independently.
- Separate an engine dependency from the simulation before selecting a WebAssembly toolchain.
How to use it
- Inventory the loop, platform calls and dependencies with license and ownership information.
- Choose one deterministic transition and create an input/output fixture.
- Port that transition first and compare outputs before wiring the browser display.
Original example
For my original tile puzzle, isolate a move-and-score step with no renderer dependency. Describe a headless test that verifies the same board and score on native and WebAssembly builds.
Limitations
A matching logic fixture does not validate input latency, audio restrictions or asset loading in the browser.
Sources and versions
The explanation and example were written for this directory. The cited files record the source version.
- Skills/reap-06-game-portability-to-wasm/SKILL.md
REA Investigation Prompts · JoasASantos ·
9756618f25·Source license MIT
Related prompts
Compare two builds to triage a crash
Use a known-good and failing build of your application to isolate what changed around a reproducible crash and hand the evidence to a maintainer.
Reverse Engineering Prompts · REA
Start a read-only application investigation
Scope the first investigation of an unfamiliar application to a small question and produce an evidence map before changing code or behavior.
Reverse Engineering Prompts · REA
Trace one feature in an application you own
Follow a single visible action from the user interface to its output. Keep observations, source evidence and hypotheses distinct so the next maintainer can verify the trace.
Reverse Engineering Prompts · REA