Built a game? Open a pull request.

Send a self-contained browser game to CyberNative-AI/games. Checks read the files. A person plays it. Then it can join the catalog.

How it ships

1. Pull request

Fork the repo. Add one folder under submissions/. Open a PR. That is the whole send path — no form, no upload portal.
2. Static checks

A first pull request from a new contributor waits for a maintainer to approve the workflow run before any check starts. That gate is one-time per contributor. Later pull requests from the same account check automatically. While it waits there is no comment and no check mark. That is not a failure. After approval, a workflow reads your files and comments pass or fail on each rule below. It does not run, build, or execute the game.
3. Someone plays it

If the checks pass, a person plays the game in a browser before merge. After it is in the catalog, the creator name is credited on the title.

One self-contained static browser game. Everything it needs to play — HTML, CSS, JS, art, audio, fonts — lives in that folder.

game-manifest.json at the folder root, with name, slug, version, entry, creator, and license.
A LICENSE file in the same folder.
Total size 20 MiB or less.
No external origins or network calls: no fetch, XHR, WebSocket, or off-repo src/href.
No inline scripts and no on* handlers. JavaScript ships as .js files.
Original work you have the right to publish — not someone else's title, art, or characters.

The entry path in the manifest must point at a real HTML file in the folder. A working layout lives in the repository.

What the checks report

Pass or fail on those file rules. Nothing else.

The comment lists each rule. It does not score fun, balance, or whether the game actually runs — that is the browser review before merge.

Failed checks: fix the listed files and push. The workflow runs again.

llms.txt is the same spec in one short file.