Lead with the outcome
State the user-visible outcome first, then list the systems that must cooperate to produce it.
Claude Opus 5 prompt for a Counter-Strike-inspired Three.js FPS
Explore Claude Opus 5 prompt for a Counter-Strike-inspired Three.js FPS: a Claude Opus 5 3D example featuring Three.js, FPS. Preview the result and adapt the prompt for your project.
a counter-strike inspired tactical FPS set in a railway station. three.js, single HTML file, all original assets.
Prompt breakdown
What this 3D prompt creates
Explore “Claude Opus 5 prompt for a Counter-Strike-inspired Three.js FPS”, a Claude Opus 5 3D example about Claude Opus 5, Three.js, FPS. 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.
Specify interaction contracts
Make controls, state transitions, collisions and reset behavior explicit; do not leave core interaction rules implied.
Add performance guardrails
Ask for asset budgets, responsive controls and graceful fallbacks so the prototype remains usable beyond a desktop demo.
Make your 3D scenes look more refined
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.
More prompts to try
Prompt for building an explorable Three.js world from a reference image with Opus 5
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.
Claude Opus 5 prompt for a CS2 and Battlefield style FPS
try making a first-person shooter that's a mix of CS2 and Battlefield.
Three.js prompt for a Leonardo da Vinci ornithopter in Claude Opus 5
leonardo da vinci ornithopter in three js