← LeaderboardThe Skill Leaderboard

openmotion-game

Build, remix, validate and locally publish playable browser games through the OpenMotion game tools, including deterministic server-authoritative multiplayer rooms and a consistent art direction.

Published by nexu-io ↗nexu-io/openmotion

Try your first task

A source-grounded starter task has not been verified for this skill yet.

SKILL.md

name: openmotion-gamedescription: Build, remix, validate and locally publish playable browser games through the OpenMotion game tools, including deterministic server-authoritative multiplayer rooms and a consistent art direction.

OpenMotion Game Studio

Turn a one-line brief into a playable local game. Resume an explicitly supplied game id; otherwise use openmotion_game_create with prompt, multiplayer and optional genre/style/setting. Read openmotion_game_get before editing. Local templates are read-only: use the market's Remix action to create an owned draft. OpenMotion does not run an internal game Agent.

  1. Interview only for missing decisions, with at most two short questions: solo/co-op/versus multiplayer mode, and whether to publish to the local market. Reuse answers and authorization already supplied.
  2. Read game design, style and genre recipes and quality floor. Choose the matching recipe (free-form briefs: pick the closest and say which) and copy its must-haves and acceptance checks into the plan. The quality floor is mandatory: a game-first full-screen playfield (never a landing-page layout with a hero headline beside a small game box), a goal readable in three seconds, at least three kinds of feedback, a 30–120 s session with a ramp, restart in two seconds or less, and characters with real silhouettes instead of bare primitives. Propose the visual direction and one English 60–90 word style formula covering rendering, shapes, palette roles, light and perspective. Preserve explicitly selected style; resolve unclear direction before costly assets. Save the formula in design/style.md and write design/plan.md with openmotion_game_write_files: experience formula, target metrics with numeric thresholds, reference route must win / idle must lose, and the wave/difficulty plan. Write design/assets.csv with at least asset, source, license and cost. Starter drafts are inputs to revise for this brief, not completed acceptance records.
  3. Optional in-game art/icon generation: discover configured media models, state the actual cost or that it is unknown, and obtain the user's spending approval before openmotion_generate_asset. Never invent a price, quota or provider capability. Poll the original job; a queued job is not an asset. No automatic paid retry. Use textures, 2D, 3D, procedural motion and audio only as needed. The game write tool accepts text, not binary uploads: use available authorized local file operations to place completed binary assets in this game's assets/; otherwise use procedural art and report the limitation. Never write binaries as text/base64.
  4. Set building with openmotion_game_set_status. Write index.html and optional client.js, style.css, logic.js, assets/** with openmotion_game_write_files, id and a batch of {path,content}. Preserve the game id and existing decisions. Read flow and logic contract before multiplayer authoring. Multiplayer shooter or 3d briefs receive the offline co-op kit, vendored Three.js and CC0 Mage/Knight characters; other briefs receive the arcade-2d kit (full-screen canvas, local fixed-step loop over logic.js, keyboard/mouse/touch/one-button input, feedback helpers, best score, portrait switch, test hook and pilot-based referenceRoute). Start from the kit you received; replace its sample rules, art and strings, keep its loop, input layer and hooks, and preserve relative paths and licenses. Rooms support late joins and 30-second session-token recovery in one local process, not internet hosting. Code controls, win/loss/restart and loading/error states, not just an attractive scene.
  5. Before publication run openmotion_game_simulate twice with the planned player count and tick budget: scripts:"reference" must finish with winners, and scripts:"idle" must finish with no winners and the intended loss state. A tick-budget timeout is not a loss. Use the game-provided exported referenceRoute(playerIndex) or explicit tick routes; keep these ordinary validated actions, never state edits. Record exact inputs, terminal ticks, summary and known limits in design/verification.md. Run openmotion_game_validate; fix diagnostics and address advisory warnings for missing covers or fewer than 20 approximate changed starter-kit lines. A low line count is a signal to inspect the requested gameplay, not an instruction to add filler. Read the rubric. Never operate, attach to or capture the user's visible browser, existing Chrome profile or desktop. Use openmotion_game_playtest for server-owned headless testing, with 1–4 clients sharing a room and meaningful per-client key/mouse scripts. Review console errors, failed requests, screenshots, roomJoined/playerCount and RAF pacing and each pass/fail assertion. The kit exposes window.__omGame={getState,getStats,sendAction} and ?debug (FPS, draw calls, entities, tick). Playtest reads authoritative snapshots, verifies player count and phase, requires scripted net displacement >0.5 world units by default, and checks horizontal overflow at 390×844. Missing hooks fail state assertions; omitted scripts perform a short W movement on each client. Test both players' movement/skills, plus deterministic rule tests for damage, revive, cooldowns and restart. Co-op defaults allow one player to start. Touch controls are required; distinguish implemented touch controls from actual touch-device acceptance. If Chrome/loopback is unavailable, report the exact blocker and unverified checks; never fall back to the user's browser.
  6. Set concise title/description/controls and zh-CN translations through openmotion_game_update_meta. Use openmotion_game_capture_cover for every gameplay cover, with optional room, input actions and delay. It starts isolated headless Chrome on the server, screenshots only the game canvas/#game root at 1280×720 to assets/cover.png, and sets cover metadata. Never use a desktop/full-window screenshot containing tabs, address bars, profiles or other apps. Imported/generated image metadata must be at least 960×540 and 16:9 ±5%; image generation still requires spending approval and does not replace the game-only capture requirement. Inspect the capture diagnostics and image rather than assuming a nonempty PNG proves gameplay. Set ready after checks; publish locally only with existing publication authorization. Update design/verification.md with tested revision, inputs, thresholds, actual results and gaps; never leave starter pending rows presented as completed. Validation reports one non-blocking reminder per missing design artifact. Report returned warnings, actual screenshot paths and playtest evidence. Publish returns three nextSteps prompts, using the plan’s Follow-up opportunities section when available; show them as optional user prompts and do not execute them automatically. Server headless results do not establish human fun, real GPU/mobile performance or audible quality.
  7. Final message to the user (plain language, the user's language, no tool names, file dumps, ids or JSON): one bold line saying what is playable now (say "playable first version" when limits remain); the play link; two to four bullets on how to play, how to invite friends (multiplayer) and the controls; what was verified and what was not (human fun, real devices, sound); the cost note (no paid generation used, or the approved spend); the cover path. If asked about cost, report only exact spend from tool results, otherwise say it is unknown and name what you will not generate from now on.

For MCP-only hosts, begin with openmotion://workflow/game/start; its linked references are available through workflow resources. Model execution and optional media tools depend on the connected host's actual discovery. If openmotion_generate_asset is absent, explain that boundary; do not claim that another tool name is available without checking.

After publication: optional gameplay trailer

Offer to make a gameplay trailer after publishing. With the user's request, call openmotion_game_trailer with {id,action:"start"}, then read {id,action:"status"}. Do not claim completion until status is ready; report projectId and videoUrl. This creates a separate editable native Motion project in the user's project catalog. Use the existing project-opening operation to open it when requested. The recording is silent; no paid music or asset generation is implied. Never use the user's browser or desktop for trailer footage.

The server records three real five-second headless gameplay clips at 1280×720, builds a roughly 19-second title/highlights/Play now composition and uses the existing verified MP4 export pipeline. Chrome, ffmpeg and the pinned native export runtime must already be available; the tool does not download or install them. Automated movement/fire/skills are sampling inputs, not proof of a winning run or human acceptance. Inspect the footage and final video. Failed jobs retain their clips and any created project; report the error and unverified stages.

Mandatory multiplayer entry acceptance

Every multiplayer game joins on load from new URL(location.href).searchParams.get('room'); generate a short random room id when missing. The local play entry redirects missing-room URLs to ?room=... and preserves other query parameters on both API prefixes. The client must still handle a missing parameter for standalone/embedded use, including opaque sandbox origins where history replacement may fail. Never ask the player to type a room code or perform a Join room step.

  • Opening the game joins within five seconds, with no click or typing.
  • Lobby displays the room code, a Copy invite link button and one primary Start button; one player can start. Copy uses the current room in the invite URL. No room-code input or Join room button, on desktop or touch.
  • openmotion_game_validate passes: room-code text inputs or Join room/加入房间 buttons in index.html/client.js are blocking diagnostics. A missing room-query read is an advisory warning; static heuristics do not prove automatic joining.
  • openmotion_game_playtest reports the autoJoin assertion passed for every client before it clicks Start or executes scripts. Evidence is the room socket's joined message or window.__omGame.getState() with selfId and the corresponding player. Joining after five seconds or only after an input fails, even if later gameplay works. Report unavailable Chrome/loopback separately.

See provenance and execution boundaries; the original MIT notice is retained in LICENSE-HIGGSFIELD.