| Resource | Use it for |
|---|
| llms.txt | An index of the maintained guides and discovery files. |
|---|
| Kit catalog | Kit IDs, supported combinations, dependencies, scripts, and download URLs. |
|---|
| OpenAPI document | The public catalog and curated download endpoint contracts. |
|---|
| auth.md | Supported sign-in behavior and current limitations. |
|---|
| Agent skill ZIP | A reusable skill with create, extend, publish, and authentication references. |
|---|
Every guide also has a Markdown version. Use Copy as Markdown at the top of a guide, or choose View Markdown to open the plain-text source. HTML and Markdown are generated from the same maintained content.
GET https://spawnkit.cloud/catalog/v1.json
The response uses schemaVersion: 1 and describes rendering engines, physics, UI, telemetry, component requirements, and curated kits. Each kit includes its ID, download URL, and resolved scripts and dependencies.
Resolve supported combinations before generating or changing a project. Use IDs returned by the catalog; do not assume that any arbitrary combination of engines and modules is supported.
const response = await fetch('https://spawnkit.cloud/catalog/v1.json')
if (!response.ok) throw new Error(`Catalog request failed: ${response.status}`)
const catalog = await response.json()
const kit = catalog.kits.find((kit) => kit.id === 'phaser')
if (!kit) throw new Error('Kit unavailable')
console.log(kit.downloadUrl)
console.log(kit.scripts)
Run this example in Node.js 24 or in your agent's tooling. Downloaded archives contain standalone source projects; downloading one does not install dependencies or run the game.
Download the SpawnKit skill ZIP, extract the spawnkit folder, and add it using your agent's documented skill-installation mechanism.
spawnkit/
├── SKILL.md
└── references/
├── create.md
├── extend.md
├── publish.md
└── authentication.md
The skill directs your agent to the relevant guide. The project's AGENTS.md adds its own setup and validation instructions. Read and preserve any instructions already present in an existing game.
The OpenAPI document covers the public catalog and curated kit downloads. Authenticated project, billing, and administrative APIs are outside its scope. For the implemented command interface, see the CLI reference.
| Response | Meaning |
|---|
200 | The requested resource is available. |
|---|
404 | The kit or resource does not exist. Refresh the catalog before retrying an old kit ID. |
|---|
405 | The HTTP method is unsupported. Read the Allow header; downloads support GET and HEAD. |
|---|
Catalog v1 changes are additive. Clients should ignore unknown fields; breaking changes require a new versioned path. Prefer the URLs returned by the catalog over constructing download paths.
@spawnkit/cli supports --json for machine output. See CLI installation for package-runner and global installation commands.
- Successful commands write their JSON result to stdout.
- Login writes newline-delimited authorization and completion records.
- Live build progress goes to stderr; a failure returns a JSON error there and exits nonzero.
- Use
--dry-run --json to inspect a mutation. JSON mode is noninteractive; mutations require --yes. - Check returned status fields and preserve operation IDs when resuming or retrying.
See CLI deployment and recovery for the command sequence, and Accounts and access for local sign-in behavior.