SuperAPI AI Directory

game-build

Coding & development

View repository

Updated 10-16 09:30

About this skill

Game Build Execution

Protect the approved experience boundaries; protect the approved art boundaries only during formal production. Drive the implementation model to produce a genuinely playable candidate, and do not redo concept, level, or art direction during the build phase.

Read build-brief-contract.md. The whitebox phase must already have GAME_DESIGN.md; the complete candidate must also already have ART_DIRECTION.md. When a product decision is missing, go back to the corresponding owner; do not invent it in place in BUILD_BRIEF.

The artifact language is locked by PRODUCT_BRIEF.md ; when not locked, follow the conversation language, and do not default to producing Chinese.

Goals and Freedom

Deliver according to the platform, production engine, target runtime, display/input, scope, rating, and networking boundaries locked by PRODUCT_BRIEF. When the target toolchain is unavailable, do not automatically switch to web; it may be used only if the brief has approved an alternative runtime, and record it separately targetRuntime、testedRuntime and the uncovered items.

Formal production inherits the observable visual constraints and approved target images of ART_DIRECTION.md , and verifies focal assets in actual runtime.

BUILD_BRIEF only compresses the product boundaries, the experience facts that must be faithfully preserved, the run method, and the completion evidence; implementation details are left to the implementation model.

First declare buildStage: whitebox|production and buildPath: template|custom. An existing interaction grammar is adopted only when it can preserve the original work's unique actions, costs, and world responses; real-time feel, space, line of sight, physics, or core verbs that a template cannot cover go custom. The whitebox must also choose a form that can validate the greatest risk, and must not reduce every project to a text game.

When the current session can code, implement directly; when an external model is unavailable, deliver only the build instructions and do not claim the game has been generated. Do not send complete copyrighted original text unrelated to the prototype.

Read optional contracts according to capability

Joint Build Loop

  1. First implement a minimal but complete core loop: launch, real input, state change, result, and restart. When scope is insufficient, fix the scope, and do not pile up audit materials first.
  2. Implement the states, actions, and results of GAME_DESIGN; when using a generative model, the model only interprets input and results, and the rule engine holds the commit authority. When signature_command exists, then execute the dedicated boundaries of the optional contract.
  3. Preserve the initial state and input path that can reproduce the problem; when randomness is involved, fix the seed; after revision, replay the failing path and adjacent counterexamples.
  4. Write back the actual toolchain, install/build/start commands, and versions; for unknown values write NOT_AVAILABLE: 原因, and do not guess.

whitebox to here, run the narrowest check according to build-brief-contract 'Completion Evidence' and hand back to the design owner; after a design revision, replay the affected paths until the greatest risk has actually been exposed or the current direction is rejected.

production continue:

  1. Provide one authoritative verification command and the minimal observable state, so that game-qa can complete in one pass clean start → 核心动作 → 设计结果 → restart。
  2. Run the narrowest development checks and startup smoke, and fix build failures, blocking logs, asset failures, and crashes; target platform input, performance, packaging, or device items not covered by the alternative runtime are written into limitation.
  3. Meet the brief's targetFinish; higher completeness only handles approved focus assets and signature moments, and does not create release audits unrelated to the playable loop.
  4. Hand off to game-qa; for diagnosis, reruns, and source-of-truth rules, see the contract "Completion Evidence".

Output

Generate build/BUILD_BRIEF.md and actual candidates; production also generates an authoritative verification entry point. Screenshots, recordings, and raw traces retain only the minimal set needed for debugging.