Lead with the outcome
State the user-visible outcome first, then list the systems that must cooperate to produce it.
Explore Prompt for upgrading a zombie game to AAA-style 3D visuals in Claude Opus 5: a Claude Opus 5 3D example featuring AAA visuals, zombie game. Preview the result and adapt the prompt for your project.
Here’s the prompt I gave to Claude Code, running Opus 5 on High mode. This was spoken/transcribed with @WisprFlow hence the conversational format. PROMPT: I want you to fork this zombie project directory, and I want us to make the environment, the map, and the gameplay look AAA, just like this tweet (screenshots attached for visual reference): https://t.co/b5CzKRTbVt Right now, the game you'll see is very blocky and not realistic... I want it to look like Battlefield 6 or the latest Call of Duty, with motion blur, amazing shadows, lighting, microanimations, and all the other bells/whistles that differentiate a vibe-coded game from a studio-level game. I want the map and gameplay and logic to effectively stay the same, but the visuals and movement need a huge update. Let's not edit this directory directly. I just want you to fork it and then redo everything graphics-wise: * visual theme * movement * all the models * etc If you need new sound effects, you can do it with ElevenLabs, and you can even do new music with ElevenLabs or text-to-speech, anything. You can also use the ElevenLabs library of sound effects we already have as well. Whatever's best. For the 3D modeling of the zombies, the gun, that map, the lighting, everything, the motion blur, the movement systems, how smooth it is, how your camera shakes when you run, all that stuff: that's gotta get to that level of quality of latest Battlefield/COD. Work until you are done. Test using browser if you need. And just have many recursive loops until its fully up to AAA standards. (note: attached screenshots of Matt's video for visual reference)
Prompt breakdown
Explore “Prompt for upgrading a zombie game to AAA-style 3D visuals in Claude Opus 5”, a Claude Opus 5 3D example about Claude Opus 5, AAA visuals, zombie game. Check the evidence label to see whether the text is an original prompt or a brief adapted from the public source.
Keep the core outcome, then specify the camera, controls, lighting and what a successful result should do. Test that first before adding more visual detail.
State the user-visible outcome first, then list the systems that must cooperate to produce it.
Make controls, state transitions, collisions and reset behavior explicit; do not leave core interaction rules implied.
Ask for asset budgets, responsive controls and graceful fallbacks so the prototype remains usable beyond a desktop demo.
Your prompt builds the game or scene. Bring it to life with more detailed characters and props, created in Tripo to replace simple placeholder models.
Build an explorable 3D world in Three.js based on the attached image. Requirements First-person controls (WASD + mouse look), collision detection, no clipping through geometry AAA visuals: PBR materials, HDRI-based lighting, real shadows, post-processing (tone mapping, bloom, AA) Physics on anything that moves or can be interacted with 60fps on a mid-range GPU Process Split the work into independent streams: terrain, props/geometry, materials/textures, lighting, physics, controls/camera, performance. Assign one sub-agent per stream. Each sub-agent owns its stream end to end and reports what it built plus what is still weak. Integrate, then run a review pass: walk the world, list every visible defect, fix them. Repeat that loop until a full pass produces zero defects, or until 5 loops. Report anything unresolved either way. Deliver a single runnable project plus launch instructions.
try making a first-person shooter that's a mix of CS2 and Battlefield.
leonardo da vinci ornithopter in three js