Tips for your first game
How to go from an idea to something you want to play again: where to start, how to describe a game to a coding agent, and how to make it better one round at a time. New here? Start here first.
Your first 30 minutes
Change Star Courier first
The template comes with a small arcade game. Asking for a change to it is the quickest way to see the whole loop work, from your request to playing it on your Deck, PC or phone, before you invest in an idea of your own.
Make Star Courier two-player, with a second ship on the right stick.
Then make something small
One mechanic, one screen, a run of one to three minutes. A tiny game you replay ten times beats a big one that’s half-finished. You can grow it later: every change builds on the last.
Know what to expect
The agent asks a few quick questions (how it should feel, 2D or 3D, the art style, games you love) and shows you a one-page plan. Once you approve it, it builds the game, draws its cover art, checks it runs and pushes. Merge its pull request and the game is in PushPlay about two minutes later.
How to describe a game
A good request is a familiar game, one twist, a theme, and how it should feel. You don’t need to know how to make games: describe the game you want to play.
- Name games it should feel like. “Feels like Vampire Survivors” says more than a paragraph of rules.
- Say who’s playing. Solo, two people sharing one screen, online, or a party game on a TV with phones as controllers.
- Describe the feeling. Tense, cozy, chaotic, clever, funny: the agent turns that into speed, difficulty, sound and art.
- Say what you don’t want. “No text tutorials”, “no timer”, “nothing scary”.
- Answer the questions. The answers go into a
DESIGN.mdnext to the game that every later change follows. In a hurry? Say “surprise me” and the agent picks for you.
Making it better
- Play it, then describe the feeling, not the fix. “It gets boring after a minute” or “jumping feels floaty” works better than “make enemies 20% faster”: the agent is set up to diagnose why, and the fix is often something you wouldn’t have guessed.
- One change at a time. Ask, play, ask again. Small rounds beat a long wish list, and it’s easy to tell what made it better.
- Ask for an audit. The template has a definition of done: a retry in one press, a difficulty curve, feedback on every action, a score to beat. Asking the agent to check against it usually finds the biggest, cheapest wins.
Requests that work well
It gets boring after a minute. Make it better.
Jumping feels floaty. Make it feel tight.
Make hits feel crunchier.
Add a boss at the end.
Add upgrades between runs.
Add music and sound effects.
Make the cover art pop at small size.
Add a two-player mode on one screen.
Check it against the definition of done and fix the biggest gaps.
When something goes wrong
Playing and sharing
- Try changes on a computer first. In a clone of the repo,
npx github:Visual-Zone-Development/pushplay-kit devplays it in a browser in a second; runnpx github:Visual-Zone-Development/pushplay-kit dev --hostto open it on your phone over Wi-Fi too. Then play the real thing on your Deck, PC or phone. - One repo, every game. Ask for your next game in the same repo. Each one gets its own tile in the library, and nobody has to watch anything new.
- Share with friends. They install PushPlay and watch your repo: paste its URL if it’s public, or add them to it on GitHub if it’s private. Every game you push reaches them too.
Prompt gallery
Ideas to copy, change and make your own. Paste one into your coding agent in the games repo.
Make a game where you defend a breakroom from a storm of paper airplanes. Swat them with a stapler. Short, frantic runs with a high score.
A platformer where you’re a frog and your tongue is a grappling hook. Swing between flies across short levels. Cozy pixel art, feels like Celeste.
A Vampire Survivors-style game where you’re a lighthouse keeper fending off sea creatures at night. Pick an upgrade every level, 10-minute runs.
A sliding-block puzzle game about tidying a messy desk. 30 hand-made levels that get trickier, with undo and a hint button. Calm, clean vector art.
A top-down racer with shopping carts in a supermarket after closing. Drift around aisles, grab items for boosts, race three CPU carts.
Two-player co-op on one screen: one player steers a leaky boat, the other patches holes with a bucket and planks. Chaotic and funny, like Overcooked.
A party game played on the TV with phones as controllers: everyone secretly draws a monster, then everyone votes on which one wins each fight.
A 3D low-poly game where you glide a paper plane through a canyon, collecting rings. Soft colors and relaxing music. Surprise me on the rest.
A turn-based dungeon crawler on a small grid, like Into the Breach but solo. Every enemy shows its next move. Each run is a new random dungeon.
A rhythm game where you’re a drummer in a marching band. Hit the beat to keep the band in step. Three songs, generated with the game’s own audio.
Make Star Courier two-player, with a second ship on the right stick.
Pitch me three tiny game ideas I could finish tonight, then build the one I pick.