Start with a concrete game idea and the controls, style, and scoring you want.
PlayWorks creator stack
AI game generator for playable browser games
Use the AI game generator to turn a concrete prompt into a playable HTML5 draft, then inspect the result against real browser-game examples before publishing.
Prompt to HTML5 game draftPlayable examples before publishingGeneration flow built for browser games
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 space shooter where the player moves with WASD, fires with space, dodges asteroids, collects fuel, survives wave timers, and earns bonus points for clean waves.
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.
Space shooter
Waves and score pressure
Generate a browser space shooter with WASD movement, spacebar shooting, three enemy wave types, projectile cooldowns, health, score combos, result screen, restart button, and a Playworks score hook.
Reference: Nova Swarm
Endless runner
Distance and obstacle loop
Generate a side-scrolling runner with jump controls, obstacles, coins, distance score, speed ramp every 20 seconds, collision fail state, mobile-readable HUD, result screen, and restart button.
Reference: Armor Plated
Tower defense
Waves and upgrades loop
Generate a one-lane tower defense game with three tower types, ten enemy waves, upgrade buttons, lives, coin rewards for defeated enemies, survival score, result screen, and restart button.
Reference: Fortress Fall: Survival
Arcade dodge
One-screen survival loop
Generate a one-screen dodge game with keyboard and touch movement, falling hazards, shield pickups, score for survival time, clear damage feedback, result screen, restart button, and leaderboard score hook.
Reference: Armor Plated
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.
Shooter reference for waves, projectile timing, readable HUD states, fixed scoring, and replay testing.
Prompt focus: enemy waves, cooldowns, health, score hook
Shooter reference for directional movement, projectile rules, enemy pressure, damage feedback, and arena scoring.
Prompt focus: movement, projectiles, damage, arena score
Defense reference for wave pacing, upgrade decisions, survival scoring, and clear pressure over time.
Prompt focus: waves, upgrades, survival timer, score
Puzzle-arcade reference for visible objectives, short sessions, score feedback, and repeatable attempts.
Prompt focus: objective clarity, move pressure, score feedbackBefore 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.
Generation starts with constraints
Game generation works best when the prompt gives the AI boundaries. A genre name alone is too open-ended. Add screen layout, input method, scoring, enemies or hazards, and the condition that ends the run.
- Name the camera and screen format: one-screen arcade, side-scroller, top-down, or fixed arena.
- Name the input: keyboard, mouse, touch, or simple buttons.
- Name the feedback: score, health, timer, combo, wave, level, or distance.
What to inspect in the generated draft
A first draft is useful when it can be played and judged. Creators should check whether the generated mechanics match the prompt, whether the score updates for understandable reasons, and whether the player can recover after losing.
- Controls should respond immediately and match the instructions.
- Hazards should be readable before they hit the player.
- The restart loop should be obvious after a failed run.
How to improve the second prompt
The second prompt should change one or two things, not rewrite the whole game. Use observations from the playable draft: movement too slow, enemies too dense, score unclear, HUD too small, or fail state missing.
- Good follow-up: Make the ship accelerate faster and show remaining health in the top left.
- Good follow-up: Reduce enemy spawn rate for the first 20 seconds, then ramp speed every wave.
- Avoid broad follow-ups like: Make it better, add more fun, or improve graphics.
Publish only after browser proof
The generator should lead to a public browser game that players can open, understand, and replay. Before publishing, test the draft in the browser, review the public title and description, and confirm the scoring behavior matches the page copy.
- Use examples like Moonlander or Nova Swarm as quality references.
- Check public-page copy before sharing.
- Use leaderboard and rewards only after the scoring loop is stable.
Tutorial steps
- Choose a narrow game format with one clear player action.
- Write a prompt that includes controls, hazards, scoring, fail state, and restart flow.
- Generate the playable draft and test it in the browser.
- Write a follow-up prompt from what you observed while playing.
- Prepare metadata, leaderboard settings, and publish controls after the game loop works.
Mechanics to include
- Ask for visible score changes tied to player skill.
- Include a fail state so the run has pressure.
- Keep the first version to one screen or one short level.
- Use readable HUD placement and controls instructions.
- Add reward or wallet details after gameplay is stable.
Common mistakes to avoid
- Prompting for multiple genres at once.
- Forgetting restart and game-over behavior.
- Requesting advanced visual polish before controls feel good.
- Changing too many mechanics in one follow-up prompt.
- Publishing without checking how the game page explains the run.
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.
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 the full creator workflow after generating a first draft.
Compare the broader maker workflow for publishing and rewards.
Start from a shooter-specific prompt and example.
Browse prompt-ready game shapes.
Play public examples before generating your own.
Connect score submission after generation.