Inspirations

The Jump Gate

An in-engine trailer for an original space game: a 3.4 km jump gate locks its segments and ripples open before a ringed gas giant, a kilometre-long capital ship bursts through, fighters peel off past the lens and the ship burns for a distant station.

Made in Claude Code (Claude subscription) with claude-opus-5.5. The agent wrote code, looked at the preview and fixed it over several iterations. This is not a single-shot result: comparisons on this site show models in one attempt.

Starting prompt

Build "The Jump Gate": a real-time, in-engine trailer for an original AAA space game, running in the browser. Hard-science-fiction realism in one consistent cinematic look: nothing toy-like, no designs borrowed from games or films, no people anywhere (no crew, pilots or cockpits). Single self-contained HTML file; Three.js and its addons from a CDN via an import map are fine; build everything procedurally (shaders, canvas or data textures), no external models, images or other files.

The setting (1 unit = 1 m; draw the moon, the planet and the stars as directions at infinity in one sky shader):
- Low orbit, about 150 km above an icy moon: a cracked blue-white surface with long double-ridged fractures and darker mottled terrain, a hard limb with no atmosphere and a thin terminator line.
- A ringed gas giant filling half the sky, about 50° across: cream, amber and rust bands with turbulent, noise-warped edges, a large oval storm and small white ovals; limb darkening and a thin scattering halo. Ray-trace the rings' shadow on the clouds and the planet's shadow on the rings. The rings sweep past just below the camera, translucent and finely structured: hundreds of ringlets, a dark division, soft edges, the planet visible through the thin parts.
- A sparse star field, mostly faint with a few bright stars, hidden by the planet and dense rings; a faint Milky Way band; a small, hot sun.
- The jump gate, 3.4 km across: an armoured ring about 220 m thick with procedural plating, instanced greebles, glowing conduits on its inner face and 24 heavy segments sleeving the ring, each with a pair of emitter prongs. Maintenance drones with blinking lights crawl along the rim for scale.
- The capital ship, about 1.1 km long, an original design with big readable shapes first: a long armoured spear of flattened diamond section with a clear bow, raised spine, sloped upper decks, a flank blade with a dark red edge along each side, a low stepped command deck and a broad engine block; greebles last and sparingly. Lit hangar bays under the blades, window bands, running lights with chase lights along the blades, and three large and four small conical nozzles with white-hot throats.
- Six unmanned 16 m fighters with twin engines (no canopy).
- A distant orbital station about 30 km away (a hub, a habitat wheel, solar arrays) that glints in the sun.

The gate effect:
- The segments roll on the ring until their prongs point at the centre, locking pair by pair with a heavy mechanical rhythm: each overshoots slightly and slams home with a flash of its locking lights. After the transit they fold away again.
- Jagged, branching energy arcs crackle between the prong tips as the charge rises.
- The space inside the ring ripples like a membrane and gravitationally lenses what lies behind it: in the sky shader, bend the rays that pass through the ring and add travelling ripples.
- The ship's arrival is a white flash with an expanding shockwave ring; the hull slides out of the membrane with a glowing seam where it crosses it.

The look of a high-budget game cinematic:
- Physically based materials with image-based light from the sky, panel tones in several greys plus a dark red accent, seams with normal detail, cavity occlusion in recesses, sun glints and rim light, shadows.
- HDR, ACES filmic tone mapping, sRGB output, bloom, horizontal anamorphic streaks, a few sun lens ghosts, volumetric engine plumes, subtle film grain, a vignette and slight chromatic aberration.
- Dramatic but readable, never muddy or washed out. Widescreen; on a portrait phone keep the frame full by widening the view.

The trailer, one 60-second loop driven by wall-clock time (performance.now):
1. Arrival (0–10 s): a slow drift across the gas giant's rings that pushes in until the gate fills the frame, already powering up: segments lock, arcs build, the membrane ripples. At about 6.6 s the flash and the shockwave; the camera swoops low and close as the bow bursts out. The 8 s frame is the thumbnail: the bow, a third of the frame, sliding out of the rippling membrane with a glowing seam, the gate's arm and the gas giant behind.
2. The hull (10–24 s): a hero tracking shot a few tens of metres off the hull, from the bow back to the engines, showing kilometres of plating, greebles, windows and hangar bays, the stern still sliding out of the glowing membrane.
3. Fly-by (24–33 s): the six fighters drop out of a hangar bay, form up, then peel off one by one past the camera with glowing engine trails; the last one whips past the lens.
4. Ignition (33–45 s): from behind the engines, the main drives ignite with a flash, the plumes lengthen and the ship accelerates towards the distant station.
5. Departure (45–60 s): from far ahead, the accelerating ship roars past the camera, then a wide shot of the gate as it starts its next cycle; the camera drifts back to the opening framing so the loop is seamless. A small, elegant title "THE JUMP GATE" fades in and out between 48 and 56 s.

Interface: nothing but that title. Everything moves on its own from the first frame: no loader, fade-in or title card. It works on a phone.

Engineering rules (the page must work on the first load, with no fixes):
- Use Three.js r170 and only methods that exist on each of its classes. Give every custom ShaderMaterial `fog: false`, and declare every uniform, constant and varying its shaders use.
- Declare each identifier once. Inside one calculation, never reuse a shared scratch vector for two values that are both still needed; use local vectors.
- Guard every animated value against NaN. Cap the pixel ratio at 2 and warm up the shaders with compileAsync before the first frame. The page runs in a sandboxed iframe, so do not use localStorage or other storage.
- Answer with the complete file exactly once, in a single ```html code block: no drafts, partial snippets or notes.

Keep planning brief and write the code. Aim for roughly 1,000 to 1,400 lines, compact and well structured.