Start with a concrete game idea and the controls, style, and scoring you want.
PlayWorks creator stack
Create a game with AI and publish it
Move from idea to playable game by describing one focused loop, testing the generated browser draft, and preparing publishing details only after the game works.
Build loop
Move from idea to playable browser build without leaving the creator flow.
Describe the game you want and generate a playable draft.
Publish with leaderboard and reward settings when the build is ready.
Prompt starting point
Make a platformer where a robot jumps between moving platforms, avoids spikes, collects coins, reaches a goal door before the timer ends, and earns bonus score for remaining time.
Start with a game loop, not a feature list
The fastest path to a useful AI-created game is one loop the player can learn quickly. Decide what the player does every few seconds, what creates pressure, and how the run ends.
- Loop: jump, dodge, collect, shoot, land, rotate, or defend.
- Pressure: timer, fuel, enemies, hazards, moves, waves, or speed.
- Outcome: score, survival time, level completion, rank, or reward eligibility.
Write the first creator prompt
A good first prompt gives Playworks enough structure to create a draft you can test. Include genre, controls, camera, scoring, hazards, fail state, restart flow, and any public-page expectations.
- Mention browser controls such as arrow keys, WASD, mouse, or touch buttons.
- Ask for HUD text that explains score, health, timer, or objective.
- Ask for clear game-over and restart behavior.
Test before you refine
Play the first draft before writing the next prompt. A useful refinement comes from a real observation, such as jump height, enemy speed, timer pressure, score clarity, or mobile readability.
- Play at least three short runs.
- Write down the first thing that blocked understanding.
- Refine the biggest blocker before requesting more content.
Prepare the public page
A game is easier to share when the public page explains the loop clearly. The title, description, cover art, and leaderboard copy should match what players will experience in the first run.
- Use a title that names the actual game, not the prompt category.
- Describe the objective and controls in player language.
- Check reward and leaderboard language after the score behavior is final.
Tutorial steps
- Choose one genre and one core action.
- Write a first prompt with controls, camera, hazards, scoring, fail state, and restart flow.
- Generate the playable draft and test it like a new player.
- Refine one improvement from playtesting.
- Prepare title, description, cover, leaderboard, and reward settings before publishing.
Mechanics to include
- Name the player objective in one sentence.
- Ask for the game to show controls inside the UI or start screen.
- Use one score rule players can understand immediately.
- Keep level length short until movement feels good.
- Treat publishing as a release step, not the first step.
Common mistakes to avoid
- Trying to create a full franchise in the first prompt.
- Leaving out the fail state because the idea sounds simple.
- Refining the visual style before testing controls.
- Publishing with placeholder metadata.
- Adding leaderboard or reward copy before score rules are clear.
Playable proof
A published arcade lander with fuel pressure, soft-landing scoring, public play, and leaderboard-ready replay pressure.
A fast browser Snake example with simple controls, clear scoring, collision rules, and quick restart behavior.
A space shooter reference with waves, keyboard movement, projectile timing, seeded scoring, and Playworks SDK hooks.
A public action game example for creators who want to inspect browser controls, game-page copy, and leaderboard proof.
Next actions
Related tutorials
Walk through prompt writing, first-draft testing, refinement, and publishing preparation.
Review browser-first controls, game loops, public pages, and player expectations.
Prepare title, description, preview, validation, and release checks before publishing.
Related paths
Use a platformer-specific prompt path.
Follow a deeper step-by-step workflow.
Review the broader creator and publishing path.
Create from plain-language prompts.
Pick a proven game shape before starting.
Inspect public games before publishing your own.