What indie puzzle game development actually looks like, solo
Solo development doesn't mean doing a studio's job alone — it means every scope decision has to earn its place, because there's no one else to absorb the cost of a wrong one.
Studio Practice
Why large language models and procedural algorithms solve different problems, and where they belong in a small studio's toolchain.
Last reviewed 2026-07-17 · Signal Notes
Key takeaway: AI generation and procedural generation are often conflated, but they serve entirely different purposes. Procedural generation scales content based on rules; AI accelerates the creation of the rules themselves.
Procedural generation is mathematical and deterministic. When a game generates a dungeon layout using cellular automata, it's following a strict set of human-authored rules. It scales by running those rules countless times. AI generation, particularly with large language models, operates on statistical probability. It scales by interpolating patterns from vast datasets. For a puzzle game, these two approaches pull in opposite directions.
A good logic puzzle requires absolute certainty. If a player deduces a solution, the system must honor the logic perfectly. Procedural generation can be carefully constrained to guarantee solvable puzzles—like generating a Sudoku board. AI generation, however, is prone to "hallucinating" or bending rules, making it fundamentally unreliable for creating the strict, interconnected logic constraints that define an elegant puzzle. It cannot be trusted to generate the puzzle itself.
Instead of generating the game's content, AI belongs in the tooling that helps build the game's engine and systems. It accelerates writing the procedural algorithms. We use AI to scaffold the level editor, write testing scripts, and quickly prototype mechanics. Procedural generation builds the levels; AI builds the tools that build the levels.
Related notes
Solo development doesn't mean doing a studio's job alone — it means every scope decision has to earn its place, because there's no one else to absorb the cost of a wrong one.
The best use of AI for a solo developer is discarding bad ideas faster, not polishing good ones.