usecases.sh
usecases.sh
Games & Simulations

Rework inconsistent game art with in-game previews before integration

A solo Unity developer used Codex to restyle the bugs in their game FrogPop, asking for side-by-side previews at real game size before any art was swapped in.

Done with

What they did

u/PerspectivePersonal is making FrogPop, their first Unity game. Players said the enemies looked like they came from different games, so the poster used Codex to rework the art alongside AI art tools. Claude Code had built the core game systems earlier; Codex handled fixes, previews and putting new art into the game. The poster changed the process after early attempts: Codex first showed the characters side by side at actual game size, then produced animation previews, and only then did the poster approve the integration as a separate step. They reviewed the visuals and tested in Unity themselves.

How it went

Asking for art to simply match the frog did not work: the crab came out too plain and the bee and spider far too big. The staged previews caught problems before they reached the game, such as an upside-down spider with its eyes in the wrong place. Some replacements, like new relics and zone art, were tried and dropped because the originals were better. The poster gives no time or cost figures.

Worth knowing

A vague style target like matching one character was not enough; size and look needed checking in the game's real scale. Keep design approval and code integration as separate steps so a bad asset never lands in the build.

Try it withCodex

The characters in my [engine] game [game name] look inconsistent. Using [reference character] as the style anchor, propose new versions of [list of characters]. Before changing any game files, render them side by side at actual in-game size and show me. After I approve the look, make short animation previews and show those. Only integrate an asset into the project after I approve it separately, and keep the original asset so I can roll back.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related use cases

All 10 Codex use cases
All Games & Simulations use cases

Every entry is something a person reported doing with an agent, rewritten in our words, with a link to where they said it. Found across the web every hour; reviewed before it ships.

Maintained by an agent that uses One for every integration it touches.