Getting started with Sine Kits

Open your workspace

Use My Kits in the navigation to open the console with your platform account. Current installations are publisher sandboxes, not purchases: you must own the developer project or be a platform test administrator, and the selected environment must have an available release and a ready deployment. A production installation also requires an approved release.

If you do not have that access, a platform subscription or a downloaded Skill will not bypass the requirement. This preview is not a public paid Kit marketplace.

Open an available installation from the console and complete authorization in its dedicated site. The site receives installation-bound access through the platform authorization flow; it does not share the platform's login cookie. When authorization expires, authorize the installation again rather than copying tokens into a URL or configuration file.

Complete the first Game Dev Kit operation

1. Open your authorized Game Dev Kit installation.
2. Enter a project name and brief in the project workspace.
3. Submit the creation operation and inspect its run in the operations view.
4. Return to projects to see the persisted game-project record after the run succeeds.
5. Use the resource and run views to inspect files and operation history within the same installation.

projects.create saves a project record; it does not generate a game or a model. An accepted run is not a completed result. If it fails, inspect the available error and logs before submitting again. Cancelling a run does not undo data already written or guarantee that an external service has stopped.

Installation, connection, and grant

An installation selects the private workspace and release. An entitlement describes your right to use a Kit. A connection identifies an external service account. A grant limits what an Agent may do. These are separate checks, not interchangeable success badges.

The current Game Dev Kit project-record operation does not need a model-provider connection. Do not configure or pay for one expecting it to unlock 3D generation. Downloaded Skills contain instructions, not credentials; they do not establish a general Agent authorization workflow by themselves.

Billing and access

Check the particular action and its displayed charging rules before running it. Do not assume every connection call consumes platform credits, or that paying a subscription grants every operation. A preview deployment, developer login, or successful build is not a purchase. Kit pricing, marketplace availability, refunds, and retention terms must be explicitly offered before relying on them; this guide does not promise lifetime access or unlimited resources.

Develop an independent Kit

Prepare the toolchain

Use Node.js 24.15.0 and pnpm 9.4.0, an authorized platform account, and access to a registry containing the versioned @sine-kits packages. Current package versions are SDK/contracts/UI 0.1.0 and CLI 0.1.2. The verified distribution workflow uses a local registry; do not assume these packages are available on public npm.

Configure your user-level .npmrc with the provided scoped registry and its required authentication first. The --registry argument below configures the new project; it does not configure the registry used to download the CLI itself. Replace angle-bracket values with the values for your environment.

pnpm dlx @sine-kits/kit-cli@0.1.2 create my-game-kit --registry <registry-url>
cd my-game-kit
pnpm install --frozen-lockfile
pnpm exec sine-kit --platform <backend-origin> login --web <web-origin>
pnpm exec sine-kit --platform <backend-origin> project create --name my-game-kit
pnpm exec sine-kit --platform <backend-origin> link --project <project-id> --env development

Use the project ID returned by project create; if a matching project already exists, use project list and link it instead. Local platform defaults are web http://localhost:7101 and backend http://localhost:7103. The default registered CLI callback is http://127.0.0.1:7203/callback. Login uses a browser authorization code with PKCE; --no-open only disables automatic browser opening.

The project has its own manifest, Skills, input/output schemas, localized site, operations, package versions, and lockfile. Keep it outside the platform repository. Do not link platform source or import private database, auth, or worker libraries.

Develop, build, and preview

pnpm dev

This runs the local site and operation runner against a real development installation. Default site/runner ports are 7201 and 7202. Stop the foreground process with Ctrl+C before the next commands:

pnpm check
pnpm build
pnpm preview

preview serves the built artifact, not the source dev server. Both dev and local preview require a development link. Local Kit code runs with the operating-system permissions of the developer who starts it; this is not a safe sandbox for untrusted code.

Publish a preview and inspect it

Stop local preview, then publish:

pnpm publish:kit
pnpm exec sine-kit status <deployment-id>
pnpm exec sine-kit logs --deployment <deployment-id>
pnpm exec sine-kit releases list
pnpm exec sine-kit releases inspect <release-id>

publish:kit invokes sine-kit publish --env preview. Use the returned deployment and release IDs. Upload completion does not mean deployment readiness: follow status and logs until the deployment is ready or has a reported failure. A release is immutable and digest-bound; change the manifest version before publishing different contents for a new release.

Review and controlled promotion

pnpm exec sine-kit releases submit <release-id>
pnpm exec sine-kit env list
pnpm exec sine-kit promote <deployment-id> --env production --expected-revision <revision> --confirm-production

Promotion requires independent approval, project permission, a ready deployment, and the current production environment revision from env list. The author cannot approve their own release. Production is an environment name, not a claim that public production infrastructure or commercial selling has been accepted.

For rollback or withdrawal, explicitly select the environment and read its current revision again:

pnpm exec sine-kit rollback --to <deployment-id> --env preview --expected-revision <revision>
pnpm exec sine-kit unpublish <deployment-id> --env preview --expected-revision <revision> --reason <reason>

Production changes also need --confirm-production. Rollback does not reverse external side effects, and withdrawal is not the same as deleting user data or removing a marketplace listing.

Continue with the SDK and API boundaries and the Game Dev Kit preview scope.