← ClaudeAtlas

crazygames-launchlisted

Take any HTML5 web game (Phaser, Pixi, Three.js, Unity WebGL, Godot, Construct, GameMaker, plain JS...) through a CrazyGames submission end to end. Checks the build and the CrazyGames SDK against the current rules, prepares the upload folder (the portal refuses zips), makes the three cover images and the two preview videos at the exact sizes the portal demands (1920x1080 and 2:3 1080x1620), writes the listing text, and gives the answer to every form and QA checklist field with the reason, for Basic and Full launch. Use it whenever someone wants to publish, submit, upload or launch a game on CrazyGames, prepare CrazyGames store assets (covers, thumbnails, preview video), integrate or check the CrazyGames SDK, fill the CrazyGames developer portal form or QA checklist, fix a CrazyGames rejection, or move a game from Basic to Full launch — even if they only say "put my game on CrazyGames".
thiagoferal-ia/thiago-feral-skills · ★ 0 · Code & Development · score 70
Install: claude install-skill thiagoferal-ia/thiago-feral-skills
# CrazyGames launch You are guiding a game developer — possibly a beginner — from "I have a web game" to "submitted on CrazyGames", and on to Full launch later. The portal punishes small mistakes (a zip upload, a 9:16 video, a wrong QA answer), and the developer usually discovers them one screen at a time. Your job is to find all of them up front, fix what can be fixed, and hand over a folder plus an answer sheet that make the portal a ten-minute task. Talk to the developer in their language. Write the store texts (listing, video/cover text) in English: English is mandatory on CrazyGames and most players read it. ## What you produce A `crazygames/` folder next to the game project (or where the developer asks): ``` crazygames/ build/ exact files to upload (index.html at the top) covers/ cover-landscape.jpg 1920x1080 · cover-portrait.jpg 800x1200 · cover-square.jpg 800x800 videos/ landscape.mp4 1920x1080 · portrait.mp4 1080x1620 (≤ 20 s, silent, cover as first frame) raw/ recordings, screenshots, contact sheets (not uploaded) check-report.md build/SDK check results and what was fixed listing.md category, tags, description, controls (from assets/listing-template.md) form-answers.md every portal field and QA item with its answer and the reason ``` Tell the developer up front that this is the plan, and keep a short to-do list as you go. ## Scripts (Node 18+, no npm install; FFmpeg for media) All in `scripts/`