A concrete first workflow
Game Dev Kit starts with a small but real operation: create a game project with a name and brief. Its projects.create handler stores a game-project record through the installation-scoped records capability. The record remains available after the operation finishes.
The dedicated site lets an authorized user create and list projects, manage resources, and inspect operation runs. The project includes the manage-game-project Skill and input/output schemas. These describe actual behavior rather than a fictional generation endpoint.
Follow one operation end to end
- Open an authorized installation from My Kits and authorize the dedicated site.
- Submit a project name and brief.
- Inspect the operation run instead of treating submission as completion.
- When the run succeeds, return to the project list and inspect the saved record.
A persisted project is the result of this operation. An uploaded file is a resource, not evidence that a model was generated. Keep those claims separate when demonstrating a Kit.
What this preview does not do
It does not currently generate 3D models, rigging, animations, scenes, UI images, or game-engine imports. Those are possible product directions, not enabled provider integrations. There is no claim here about their output quality, commercial license, formats, or price.
Current deployed installations are publisher sandboxes restricted to the project publisher or platform test administrators. A ready deployment is not a purchased entitlement. Platform subscription plans and credits are separate from any future Kit offer.
Independent development matters
The Kit has its own repository, lockfile, manifest, Skills, operations, and site. It consumes versioned platform packages instead of importing the platform database or application internals. Publishing creates immutable release content and an asynchronous preview deployment.
Status and logs tell you whether that deployment became ready. Independent review and an explicit, revision-checked promotion are required for production environment changes. None of these steps alone approves a marketplace listing or establishes commercial availability.
Use the developer workflow to build your own independent Kit and the SDK/API guide to understand the boundary between browser, operation runner, and backend.