Kraig Adams

Games

Small games I make with AI. Watch a short video of each one, play it, or read how it was built.

Kindlewatch

A tiny pixel land seen from far above. Gather, craft, farm and build a shelter before night falls.

Keyboard and mouse. Walk with WASD or the arrows, hold the mouse on a tree or a stone, and press E for your inventory. Your first night falls after about eight minutes.

Kindlewatch is made for a computer. Watch the video here, then open this page on a laptop or desktop to play.

PlayBehind the scenes

Played it? Tell me what to fix.

01More games

  • Solhex

    Build a space station factory from one hex, and fight with real space physics.

    Mouse and keyboard. The first few minutes point at what to click next. Part One is about four hours.

    Solhex is made for a computer. Watch the video here, then open this page on a laptop or desktop to play.

    PlayBehind the scenes

    Played it? Tell me what to fix.

  • Jumpgate

    A tiny probe, its drones, and a factory that grows in empty space until it can build a gate.

    Mouse and keyboard. A test player takes about four and a half to five hours for all ten chapters.

    Jumpgate is made for a computer. Watch the video here, then open this page on a laptop or desktop to play.

    PlayBehind the scenes

    Played it? Tell me what to fix.

  • Sapper

    A cave tower defense. Dig, build and hold the dark with your squad, six floors down to the queen.

    Keyboard and mouse. Move with the keys and aim your light with the mouse. Walk into rock to dig it. You get one life.

    Sapper is made for a computer. Watch the video here, then open this page on a laptop or desktop to play.

    PlayBehind the scenes

    Played it? Tell me what to fix.

02Built for phones

03Want to make games like this?

I design these games and play every build. Claude, Anthropic's AI, writes the code.

How I make them

  1. I describe the game in plain words: what you do, how it should feel, and how long a win should take.
  2. Claude builds a first version I can play in a browser, usually the same evening.
  3. I play it and say what felt wrong in my own words. Claude changes it and I play again, one build at a time.
  4. A test player written in code plays every build too, so what breaks is caught before I see it.
  5. I fix the first ten minutes before I add anything deeper.

How you can

  1. Get an AI that writes code. I use Claude Code.
  2. Start small: one screen and one thing to do, playable in a browser.
  3. Play every build yourself. Say what you felt, not how to fix it.
  4. Keep a note for each build, so you can see what changed.
  5. Let a few strangers play early, and watch where they stop.

More on how I work with AI: