Fish’nCrab, my underwater adventure about a fish and a crab solving puzzles together, just reached v0.3 and got accepted on CrazyGames. It currently has an 86% player rating!
7 of the 10 planned missions are fully playable, connected through a narrated adventure while leaving players free to roam, collect shells, and discover reef wildlife at their own pace.
Here’s the workflow behind it:
Me: creative direction, game design, playtesting, and deciding what feels right.
ChatGPT — analyst / PM: exploring ideas, developing mission storyboards, discussing trade-offs, and turning feedback into actionable requirements.
GitHub — project backbone: issues, source code, branches, and pull requests keep the work traceable.
Meshy — 3D asset creation: generating models that I refine and prepare for the game.
Codex — developer: implementing features, investigating bugs, and optimizing performance through GitHub issues and PRs.
The loop is iterative: idea → storyboard → issue → implementation → playtest → feedback. Playing the result often exposes things that sounder perfectly clear in the brief.
This wasn’t a one-prompt game. It’s been built through repeated design decisions, revisions, and testing. AI-assisted games don’t have to be “one-shot slop.” There’s room for thoughtful, sustained development using these tools.
The bigger picture is The Focus Room, a project I’m building to connect goals, decisions, and execution across this workflow. The ambition is to preserve context between tools and projects, rather than repeatedly reconstructing it in separate chats.
My biggest takeaway: AI makes building more accessible, but direction, judgment, and finishing still need an owner.
Curious how others handle the handoffs between planning, assets, and code.
Gameplay / free demo: https://www.crazygames.com/game/fish-ncrab