Start with a concrete game idea and the controls, style, and scoring you want.
PlayWorks creator stack
AI game maker for browser games and rewards
Describe the game loop, controls, score rules, and win condition. Playworks turns that prompt into a browser-playable draft you can test, improve, and publish.
Prompt to playable HTML5 draftPublic game pages with real examplesLeaderboard and reward controls after testing
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 lunar lander arcade game with keyboard thrust, limited fuel, terrain hazards, soft-landing scoring, a restart button, and a daily leaderboard score hook.
Choose what you need next
Use the page as a short path instead of reading every section in order.
Prompt examples by genre
Copy a complete starter prompt, then change the controls, theme, scoring rule, or win condition.
Arcade lander
Precision landing loop
Make a lunar lander arcade game with arrow-key rotation, spacebar thrust, limited fuel, uneven landing pads, soft-landing score, crash state, result screen, restart button, and leaderboard score hook.
Reference: Moonlander
Classic Snake
Growth and collision loop
Make a Snake game with arrow-key controls, food pickups, growing length, wall collision, self collision, speed increases every five pickups, score UI, pause state, result screen, and restart button.
Reference: GalaSnake
Space shooter
Waves and projectile timing
Make a browser space shooter with WASD movement, spacebar shooting, three enemy wave types, projectile cooldowns, health, score for each enemy, result screen, restart button, and leaderboard score hook.
Reference: Nova Swarm
Platformer
Jump, hazard, and goal loop
Make a side-view platformer with arrow-key movement, spacebar jump, three platforms, spike hazards, coin pickups, goal door, timer bonus, result screen, restart button, and final score submission.
Reference: Armor Plated
Endless runner
Distance and obstacle pressure
Make an endless runner with jump controls, low and high obstacles, coins, distance score, speed ramp every 20 seconds, collision fail state, mobile-readable HUD, result screen, and restart button.
Reference: Armor Plated
Tank arena
Projectile combat loop
Make a top-down tank arena with WASD movement, mouse or arrow-key aiming, slow projectiles, destructible cover, enemy waves, health, score per enemy, result screen, and restart button.
Reference: Battle Tanks
Puzzle arcade
Short-session objective loop
Make a match-and-break puzzle game with a visible target score, limited moves, bonus pieces, combo feedback, result screen, restart button, and a single final score for leaderboard submission.
Reference: Diamond Breaker
Published Playworks examples
Play a live example here, then use the public game pages as references for prompt scope, readable HUDs, scoring, and restart loops.
Playable demo
Diamond Breaker
Gary-started puzzle-arcade reference with a clean new-game start, visible score, level state, and repeatable attempts.
Inspect: new game start, score UI, level state, restart loopGary-started puzzle-arcade reference with a clean new-game start, visible score, level state, and repeatable attempts.
Prompt focus: new game start, score UI, level state, restart loop
Shooter reference for wave state, projectile timing, readable HUD states, and score testing.
Prompt focus: start state, enemy waves, cooldowns, health, score hookGary-started tank arena reference with a direct play start, combat canvas, score state, and restart control.
Prompt focus: play start, tank movement, score state, restart control
Precision arcade reference for thrust, fuel pressure, crash state, landing score, and replay pacing.
Prompt focus: thrust controls, fuel limit, landing scoreBefore and after prompt refinements
The best prompts describe the player verb, scoring, fail state, feedback, and what should happen after a run ends.
Too vague to generate a playable loop
Before
Make a fun arcade game.
After
Make a one-screen asteroid dodger with arrow-key movement, three hazard speeds, fuel pickups, score combos, collision damage, result screen, restart button, and leaderboard score hook.
The improved prompt names the player verb, hazards, pickups, score events, damage rule, end state, and publishing-ready score behavior.
Theme without testable rules
Before
Make a neon cyber game where the player survives as long as possible.
After
Make a top-down neon survival game where the player moves with WASD, dodges drones, collects battery cells for 100 points, loses one health on collision, survives for 90 seconds, and can restart from a result screen.
The revised prompt turns the theme into measurable mechanics that can be tested within the first minute.
Floaty controls and weak restart loop
Before
Make a platformer where the character jumps around and collects coins.
After
Make a platformer with short jump arcs, coyote-time forgiveness, three coin lanes, spike hazards, a goal door, a result screen that names the final score, and a restart button that resets position, timer, coins, and hazards.
The follow-up describes control feel, scoring, hazards, win state, and reset behavior instead of asking for a broad improvement.
Gary replay from a real attempt
This replays saved Gary-started public examples, not live anonymous AI generation.
Choose a starter prompt
Create a match-and-break puzzle arcade game with a paddle, colorful blocks, visible score, level state, ball reset, result screen, and a restart button.
Replay stages
- Prompt interpretationGary reads the selected starter prompt and turns it into a first-pass game brief.
- Mechanics selectionThe replay highlights the controls, score events, hazards, fail state, and restart loop chosen for the build.
- Controls and scoringThe playable draft connects input, visible HUD values, score changes, and a repeatable result state.
- SDK publish readinessThe replay checks the score hook, public page readiness, and whether the draft is clear enough for players.
- Testing checklistThe saved attempt unlocks the same public playable result so creators can inspect the draft before making their own version.
Testing checklist
Custom prompt requires sign-in
Save a custom prompt, then continue in the creator workspace.
What an AI game maker should produce
A useful AI game maker should create something you can open and test, not only a design idea. In Playworks, the target is a playable browser draft with controls, scoring, restart behavior, and a path toward publishing.
- Start with one playable loop: move, avoid, collect, land, shoot, jump, or solve.
- Ask for visible scoring, fail states, and restart flow in the first prompt.
- Use public examples to compare pacing, readability, and input feel before publishing.
Prompt anatomy for better first drafts
The best prompts describe the game like a short production brief. They name the genre, camera, controls, score events, fail state, visual style, and what should happen when the player restarts.
- Weak prompt: Make a fun arcade game.
- Better prompt: Make a one-screen asteroid dodger with arrow-key movement, fuel pickups, score combos, collision damage, and a restart menu.
- Strong prompt: Add browser-readable HUD text, seeded scoring, and a Playworks leaderboard score hook.
From first draft to publishable game
After generation, creators should test the draft like a player. The page should answer whether controls respond, scoring changes, the game can end, the player can restart, and the public page explains what was built.
- Test controls and scoring before adding more mechanics.
- Use the creator workspace to refine one improvement at a time.
- Publish only after the title, description, cover, and player instructions match the game.
Where rewards and leaderboards fit
Rewards work best after the game loop is clear. Build the game first, prove the score can be submitted reliably, then decide whether a leaderboard or creator-funded reward rule makes sense for the player experience.
- Use leaderboard scoring for repeatable runs and clean comparison.
- Use rewards only when the rules are easy to understand before play.
- Keep reward copy separate from core gameplay instructions so players know what to do.
Tutorial steps
- Write a prompt with genre, controls, scoring, fail state, restart behavior, and visual style.
- Generate the first playable browser draft in the creator workflow.
- Play the draft, note one improvement, and refine the mechanics before adding systems.
- Prepare the public game page with title, description, cover art, leaderboard settings, and reward copy if needed.
- Publish, share, and watch plays, scores, and creator analytics.
Mechanics to include
- One core loop should be playable within the first 10 seconds.
- Controls should be named clearly in the prompt and visible in the game UI.
- Scoring should change for player actions, not only for surviving time.
- Fail states and restart flow should be part of the first draft.
- Leaderboard hooks should use the final score the player understands.
Common mistakes to avoid
- Asking for a full game world before one loop works.
- Leaving out controls, score rules, or fail conditions.
- Adding rewards before score submission is easy to understand.
- Publishing with generic title or description copy that does not match the game.
- Treating the AI output as final without playing it like a new user.
Common failure modes and fixes
When a generated draft feels off, adjust one part of the prompt and run a focused revision.
The draft looks fine but the player does not know what to do.
- Likely cause
- The prompt named a theme but did not name the objective, HUD copy, or first player action.
- Fix prompt
- Add a start screen that says the objective in one sentence, show controls beside the play button, and make the first collectible or target visible within two seconds.
Scoring feels random or hard to compare on a leaderboard.
- Likely cause
- The prompt did not define exactly when score changes or what score is submitted at game over.
- Fix prompt
- Use one visible score value. Add 10 points for each pickup, 50 points for each clean objective, subtract no hidden points, and submit the final score only after the result screen appears.
Players cannot replay quickly after losing.
- Likely cause
- The first prompt skipped the fail state and restart behavior.
- Fix prompt
- When the player fails, pause movement, show final score, explain the cause, and add a restart button that resets position, score, timer, enemies, and pickups.
Controls feel floaty or delayed.
- Likely cause
- The prompt named a genre but did not define acceleration, jump height, cooldowns, or input feedback.
- Fix prompt
- Tighten movement by lowering acceleration delay, adding immediate input feedback, shortening jump hang time, and showing a clear animation or sound when movement starts.
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
Generate a playable game draft from a detailed prompt.
Follow the creator workflow from idea to publish-ready draft.
Use plain-language prompts without starting in code.
Start from genre-specific prompts and examples.
Try a focused template with a clear loop and score rules.
Open public Playworks games before creating your own.
Review the browser-specific path for HTML5 canvas output, testing, and public play.
See how wallet sign-in, leaderboards, and creator-funded reward controls fit after the game loop works.