ChatPRD work and a playable Blender fashion studio
Between ChatPRD prototype and chat work, I asked Codex to build a fashion-design game with Blender. By the afternoon I could customize an outfit, walk it down a runway, and have the agent drive a tour while I narrated.
Turn a Blender scene into a playable fashion-design app
I asked Codex to make a modern fashion-design game: customize an outfit, then walk around wearing it. I wanted it to use Blender, so the result would include a scene I could edit as well as an app I could play with.
Codex wrote and ran a Blender script, exported the assets as glTF, and built a browser interface around them. Dream Atelier let me change clothes, colors, fabrics, and accessories, save looks, and walk a runway or rooftop. Codex then used Chrome to try clothing changes, restore a saved outfit, and check the movement.
One agent carried the work from scene setup through export and into the interface. I didn’t have to stitch together separate 3D and web-development steps. I had a playable local prototype and the editable Blender file. You can see the fashion experiment in this later How I AI episode.
Have Codex operate a product demo while you narrate
Once the fashion-design prototype worked, I wanted to record a tour. I had Codex put Chrome back on the starting screen and wait for my cue. Then it drove the demo slowly enough for me to talk over it.
It changed the outfit, showed the customization controls, saved a look, and took the character onto the runway and rooftop, with pauses along the way. That let me concentrate on explaining what we had built instead of remembering the clicks while narrating. This was the on-screen demo pass; the workflow didn’t include editing or exporting the recording.
# Run a product tour while I narrate
Adapted from this workflow; not the original transcript.
Use the open browser to demonstrate [product]. First inspect the working app and propose a short sequence showing [features]. Use sample data suitable for a public recording.
Reset the app to a clean starting screen and wait for me to say go. Do not begin before my cue.
When I say go, operate the demo slowly. Pause after each meaningful change so I can explain it. Keep the cursor clear of the result where possible. If something fails, stop and tell me rather than clicking through it.
End on [desired closing state]. Leave the app there.