Game Dev
Say “I want to make a game” and Neo answers with three painted concepts before it asks a single question. The one you pick becomes the canon: palette, style, hero silhouette and tileset plan, followed by every sprite, tile and sound after it. Levels are built in Godot (live in the editor through a bridge), Unity or Unreal, and Neo checks them in the running game: a trap that should deal 30 damage is measured, not assumed.
A recreated panel in the style of the app: how a turn in this module goes, built only from what the module really does.
6 things you can do with it.

Three concepts first
Painted proposals with a pitch and a palette each. The price is on the button before anything is painted.
A canon every asset follows
The chosen concept locks the palette, the style and the hero silhouette.
The hero, from the canon
The first sprite is drawn with the locked colours, in one turn.
Real frame animation
Idle, run, jump, attack and hurt drawn frame by frame on your own PixelLab account, every strip checked.
Checked in the running game
Damage, timings and resets are measured while the game runs.
Released where players are
A Steam ready export, phones or the browser, from the same project.
Plain words in the one chat.
You never pick the module. Neo reads the request, picks Game Dev, and says why.
What you hold when it is done.
- A playable build and the engine project, in a folder you own
- An attract mode video where the game plays itself
- Art, music and sound effects that match one style
Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.