Visual Production: The One-Person Game Studio

AI can produce a character, a screen, or a working feature quickly. It can also leave you with a game whose assets do not belong together, whose details fall apart up close, and whose unfinished edges make it feel like nobody was in charge.

In Signed Off, I explain how I make games alone by treating AI as the team I direct. I replace prompt-and-accept with a production path: define the visual standard, write the brief, compare rough sketches, approve color, build a complete design sheet, inspect the final, and promote only the work that belongs in the game.

The book shows how to judge the right things at each stage, lock colors before they drift, keep generated detail honest, use simple geometry references when straight lines matter, and review a final both up close and at the size the player will see. It also covers the polish screenshots miss: stutters, weak motion, behavior without a reason, and code accepted only because it works.

No drawing or programming experience is required. The method is about deciding what right looks like, writing it down, and looking carefully enough to hold that standard from the first idea to the finished game.

Generating another image is easy; keeping the intended asset consistent is harder. I explain how I turn a game asset into a deliberate request, starting with the concept and the kind of drawing I need.

I cover how to count, place, and size important elements, decide where detail belongs, assign each reference a job, and describe what the image must not become. The book follows requests through different production stages, then shows how I revise one decision and keep the request that worked as a starting point for the next asset.

Image models still miss. The aim is to make those misses easier to identify and corrections more controlled, not to promise a perfect result.

A pleasing drawing or model preview is not yet a usable game asset. I follow a character from an approved design and multi-view sheet through a 3D route, inspection, color, rigging, and use in the game. My examples show how I resolve missing views and reject changes that break the design.

One good picture is only the beginning of a consistent 2D game. I explain how I carry a character design into sheets and sprites, inspect the frames as a sequence, and direct interface assets as a coherent set. My examples include a green slime and an interface kit, with attention to how each asset will actually be used.