A rainy Kyoto alley in Three.js, refined through screenshots
A creator-reported code-only scene built with Opus 5.5, using repeated screenshot reviews and a short list of priority fixes.
mizugame (@mizugame_22) asked Opus 5.5 for a photorealistic 3D scene of a Kyoto alley on a rainy night. The creator describes it as a Three.js project made entirely in code, without image, model, or audio files.
The reported process took 53 minutes for the first build and another 175 minutes of revision, with two manual interventions. Those timings and the asset-free implementation are the creator’s account; the project was not independently reproduced here.
Review the scene in small rounds
The creator describes 25 review rounds, taking eight screenshots in each round and selecting at most three priority fixes. That gives the agent a repeated cycle of looking at the actual result, choosing a bounded set of changes, and checking again.
Choose views that reveal problems
For a similar scene, keep a fixed set of camera positions: the entrance, the main sightline, a close view of a wet surface, and an angle that exposes object intersections. Add views for areas that changed. Consistent framing makes it easier to tell whether a revision improved the scene or merely moved the problem out of view.
Fix the largest visual errors first
Use the small fix budget to address composition, scale, and lighting before adding more props. For a rainy night scene, check whether the street remains readable, bright signs overwhelm nearby surfaces, or rain hides important silhouettes. These are suggested review criteria, not a reconstruction of the creator’s individual revisions.
Keep a record beyond the final image
Save before-and-after views with each change, and record any manual correction separately. Before reusing a browser scene, also measure frame time, test a smaller viewport, and check how it behaves when WebGL is unavailable. The post’s timings describe one run, so use your own measurements when estimating a similar project.