How To Make AI Games - Tesana AI Guide

Tesana is a prompt-to-play game builder. If you’ve used Lovable, it’ll feel familiar, except it’s built specifically for games. You describe what you want, Tesana generates a playable foundation, and you iterate by chatting until it’s fun.

Here’s the simplest way to ship a game with Tesana.

1) Describe your game concept

Start by telling Tesana what you want to build in plain language. The better your initial prompt, the better the first playable version.

Include these basics:

• Genre + camera: 2D side-scroller, top-down, FPS, platformer, RTS-style, etc.

• Core loop: what the player does every 10 seconds

• Visual style: pixel art, low-poly, neon sci-fi, cozy, realistic, grimy

• Must-have features: upgrades, enemies, levels, bosses, UI, audio, etc.

• “Feel” words: snappy, floaty, punishing, chill, arcade-y

Example prompt you can copy:

“Build a high-speed 2D roguelike shooter set in a neon trash city. Tight movement, dodge roll, 10-minute runs, random upgrades every level, and a boss at the end. Add a simple UI for health, ammo, and a timer.”

If you’re not sure what to write, don’t overthink it. A clear MVP request beats a giant wishlist.

2) Tesana builds your foundation

Once you send your concept, Tesana generates a playable starting version. This is the “get it working fast” step.

Typically your first build includes:

• Player movement + controls

• The core gameplay loop (win/lose or survive)

• Starter enemies or obstacles

• Basic UI (health, score, timer, menu)

• Enough structure to grow from

Your goal here is not perfection. Your goal is playable.

3) Refine gameplay and improve through iteration

This is where good games get made. You play the build, notice what feels off, then tell Tesana exactly what to change.

Best practice: one focused change per message. Small changes compound fast.

High-impact improvements to request:

• “Make movement snappier: faster acceleration, less friction, tighter jump”

• “Add game feel: hit flash, knockback, screen shake, sound cues”

• “Add enemy variety: a charger, a ranged enemy, a tank”

• “Add progression: upgrades every 60 seconds, 3 choices, stackable buffs”

• “Add a boss at minute 8 with 3 attack patterns”

• “Tune difficulty ramp so it’s fair for the first 2 minutes, then escalates”

• 
  

If something breaks, be concrete:

• What you did

• What happened

• What you expected

• Any error text (paste it)

Example bug report prompt:

“Bug: after level 2, enemies stop pathing and freeze. Steps: start run, survive to level 2, spawn wave 3. Expected: enemies chase player. Actual: they idle.”

That kind of message gets fixed fast.

4) Publish and start playing (and sharing)

Once it’s fun enough, publish it and get real feedback. Don’t wait until it’s perfect. Early playtests will tell you what to fix next.

What to do after publishing:

• Send it to a few friends and watch where they struggle

• Post it in Discord for feedback and playtests 🎮

• Iterate based on what people say (and what they don’t say)

• 
  

The real workflow is simple:

prompt → playable → iterate → share → repeat

A fast prompt template you can reuse

If you want a reliable starting structure, copy this and fill it in:

“Build a [GENRE] game in [2D/3D] with [CAMERA].

Core loop: [WHAT PLAYER DOES].

Style: [VISUAL STYLE + MOOD].

Must-have features: [LIST].

Progression: [UPGRADES/LEVELS/META].

Add UI for: [HEALTH/SCORE/TIMER/etc].

Make it playable as an MVP first.”

That’s it. Make something playable today, then make it better tomorrow.