Loading...
Loading...
Found 5 Skills
Evidence-based Quality Verification for Games. Launch the actual build on the selected target runtime to prove real rendering, input, core loop, at least one designed outcome, restart functionality, and explicit limitations, without framing subjective fun as a definitive verdict. This method is used for testing generated games, conducting QA on game builds, checking whether a game is fully playable, or verifying builds.
The user built or changed something visual — a UI, an animation, a game, a generated video — and wants it verified, or asks "why does my UI look wrong", "check that the fix actually worked", "does the animation glitch". Use this to record the running thing, critique the recording against plain-language pass criteria, and iterate until it passes with before/after proof.
Define creation, naming, and replacement rules for placeholder assets so the game is testable before final art exists.
Use when an AI agent (or any external script) needs to play-test a running Pixi'VN game end-to-end in a real browser — starting the game, advancing/branching the story, answering input prompts, going back, and reading/writing storage — via `Game.testing`, the opt-in devtools bridge exposed on `window`. Load this before wiring up automated/agent-driven playtesting, not for authoring story content itself (see `pixi-vn-narration`).
Use Roblox Studio MCP safely and productively from Claude. Use when connecting to Studio, inspecting a Roblox place, editing scripts or instances, inserting assets, generating models/materials, or playtesting through MCP tools.