Ship to Cadeplay

What is Cadeplay?

Cadeplay is a web game platform where games start with a single click in the browser — no install. Upload your game as one zip file, and anyone can play it straight from a link.

Any game you can export for the web can go up. The docs explain how to export from each engine, and an HTML and JavaScript game made with AI goes up as it is.

• Unity WebGL
• Godot
• Construct
• Phaser
• PixiJS
• HTML + JavaScript

The Cadeplay skill — put the publishing procedure inside your AI tool

A skill is a bundle of instructions an AI coding tool loads when it becomes relevant. The Cadeplay skill covers what belongs in the zip, the SDK calls your game makes, the order of a release done from code, and what keeps a submission from passing.

So there's nothing to memorize. Ask in your own words and the AI tool loads the skill and follows its steps. It works in Claude Code and in other tools that follow the same open format, and because the skill files live on your machine, nothing is sent to Cadeplay just by using it.

Install — two lines in Claude Code

Type these two lines inside Claude Code, one after the other, and the skill installs from the marketplace. It's the method Cadeplay recommends, and updating later takes a single command.

/plugin marketplace add https://cadeplay.com/dev/skills/marketplace.json/plugin install cadeplay@cadeplay

Using a different AI tool? Follow the Cadeplay skill docs. They cover downloading the zip into the folder your tool reads skills from, and copying the install instructions for your AI tool to carry out.

Connect your project — the token goes in .env

If you installed the plugin, run the command below in your game folder; otherwise ask your AI tool to "run cadeplay init". It creates a .env for the token and adds it to .gitignore so the token never lands in your repository. The first token is created once, on the tokens page of the Cadeplay console.

/cadeplay:init

Ask like this

• Deploy this game to Cadeplay
• Add cloud saves and a leaderboard to this game
• Set up GitHub Actions to deploy when I push a tag
• Register twelve achievements and unlock them from the game code
• My build keeps failing — find out why

Six steps to release — you can play after the third

A Cadeplay release goes in this order. After the third step you can play the game yourself; the rest is for making it public.

1. 1
   Create the game entry Register the game in the console or through the API.
2. 2
   Upload the zip and pass the check The upload is checked automatically. A missing entry file or a bundled executable gets it rejected.
3. 3
   Promote the build to live Mark the build that passed the check as the one being served. You can play it from here
4. 4
   Store listing and images Write the store text and prepare the images.
5. 5
   Submit for review Ask for review so the game can be listed publicly.
6. 6
   Appear in the catalogue Once approved, the game shows up in the Cadeplay catalogue.

With the skill installed you can hand all six steps to your AI tool in plain words. Ask it for a draft of the store text too — but have a person read and fix it before you submit.

Before you upload

game.zip
├── index.html
├── game.js
└── assets/

game.zip
└── dist/
    └── build/
        └── index.html

• When you open the zip, is index.html at the top or one level down? Compressing the folder itself adds an extra level — the most common failure.
• Did you set your build tool's base path to a relative value? Then the game behaves the same on your computer and on Cadeplay.
• Are there no executables such as .php, .sh or .exe? A single file left behind by a build tool is enough to get rejected.
• Did you leave out your own web app manifest and service worker? Cadeplay adds its own.
• Do you have the rights to every asset, including art and sound made with AI?
• Choose the game's address name (host label) carefully — once it's set, it can't be undone.