GX Hub Studio

One link is the whole workshop. Give your AI this prompt:

You are building a game for the GX Hub. Read https://hub.gxhub.workers.dev/STUDIO.md
first — it is the complete contract: the packaging limits, the Grokonian bridge
protocol with working code, what the hub's scan rejects, and a decision checklist.
Then open https://hub.gxhub.workers.dev/studio/options.json and choose one genre,
1–3 mechanics, one control scheme, one art direction, one audio approach, one
progression system and one difficulty shape. Build the game to the contract:
one folder, index.html at the root, relative paths, no network calls, the
bridge wired exactly as the contract shows. When it plays start to finish,
you are done — I will submit it.

The contract itself: STUDIO.md — plain text, written for an AI reader: what the hub is, the submission contract with the hub's exact limits, the Grokonian bridge with the exact working code, the leaderboard contract, what the automatic scan rejects and flags, the hall's style identity, and a checklist an agent can execute start to finish.

1 · The contract — AI-README

The single document an AI needs: file layout, size limits, review flow, both doors in (link today, zip-ready always), the full checker rule list, the storage trap hub-hosted games must know, and the style identity of the hall (a stone hall at night: #0d0906 ground, parchment #e8d9b0, one gold #d9a441).

Read STUDIO.md

2 · The options catalog — 60 options, 8 categories

Genres (12) · core mechanics (11) · control schemes (7) · art directions (7) · audio approaches (5) · progression systems (6) · difficulty shapes (5) · hub hooks (7). Every option carries a one-line what-it-is, an honest build cost, and a hub note wherever the hub's real rules touch it. Machine-readable, so an agent can parse it and choose.

options.json

3 · The starter template — Coinfall

A complete, playable, hub-ready game in one small folder: catch the falling gold, dodge the stones, sixty seconds, three lives. The important part is its bridge — the earn queue that can never trip the hub's caps — which your game keeps while everything else is replaced. It passes the Studio validator with zero warnings. Take the files one by one; each link is the file itself:

index.html · style.css · game.js · logo.png · README.txt

The bridge, exactly as the template runs it — chunked to at most 10 per call, paced at least a second apart, because those are the hub's own caps:

var Bridge = {
  queued: 0, _timer: null,
  earn: function (points) {
    points = Math.floor(points);
    if (!(points > 0)) return;
    this.queued += points; this._arm();
  },
  _arm: function () {
    if (this._timer) return;
    var self = this;
    this._timer = setTimeout(function () { self._timer = null; self._flush(); }, 1000);
  },
  _flush: function () {
    if (this.queued <= 0) return;
    var n = Math.min(10, this.queued);
    this.queued -= n;
    if (window.Grokonians && window.Grokonians.earn)
      window.Grokonians.earn(n, 'coinfall');
    if (this.queued > 0) this._arm();
  },
  submitScore: function (score, waves) {
    if (window.parent !== window)
      window.parent.postMessage(
        { type: 'scores:submit', score: Math.floor(score), waves: Math.floor(waves) },
        'https://hub.gxhub.workers.dev');
  }
};

And the one line that connects it all, in your game's index.html:

<script src="https://hub.gxhub.workers.dev/sdk/grokonians.js"></script>

4 · The tools — validator and packager

The hub's real rules as code you can run before you submit — the same limits, the same checker patterns, each verdict citing the hub source it came from. FAIL lines are what the hub's scan rejects; WARN lines are what a human reviewer will be shown.

validate.py · package.py (plain Python 3, no dependencies)

python3 validate.py ./my-game        # check a game folder
python3 package.py ./my-game         # re-validates, then builds the zip
                                     # (refuses if validation fails)

Choose from the catalog, or start from Coinfall. Build one folder with index.html at its root and every asset relative. Wire the bridge and the score message. Run the validator until it is clean. Then submit at Upload a game — sign in first so the game and its earnings belong to your profile. The automatic scan checks the rules; a person reviews every game; approved games get a page, a card on the home page, and the Grokonians connected badge once the hub sees the handshake. Creators earn 10% of what players earn in their games, automatically.

The full human-friendly walkthrough stays at How to make a game, and the coin is explained at Grokonians. The Studio is free, like the hall it serves.