3D & Generative · Oct 4, 2026
opus 5.5 is insanely good at 3D motion design
opus 5.5 is insanely good at… by vette, credited to Claude Opus 5.5. Watch the 3D & Generative video, explore the shared prompt and visit the original X post.
vette@0xvette
View on Xopus 5.5 is insanely good at 3D motion design this whole 15s video is code. 0 after effects. 0 blender. 0 cinema4d. one single HTML file: three.js + procedural Web Audio API mid-air explosion → bottom-up snap → spline auto-lacing → dual colorway sweep → physics drop open-sourcing the exact prompt template and technical architecture behind it grab it and build your own ↓ <inputs> Ask me for: 1. Product specs & BOM: exact millimeter dimensions and mesh parts (e.g. hex-lug outsole, 32/22 mm midsole, knit upper, heel counter, 12 eyelets, oval laces). 2. 3 colorways as calibrated hex codes (e.g. CHALK #F2EEE7, CINDER #2B2B2F, FLARE #D8322A) and typography specs. 3. Audio mood: tempo (150 BPM hype beat in D minor) and mechanical sound triggers for the Web Audio API. </inputs> <direction> High-end commercial product shot. 15.0s, 900 frames, 1080x1350 (4:5 vertical) at 60 fps. One HTML file using Three.js 0.160. One camera take, FOV 28, zero cuts: 40° orbit during explosion, push-in…
The prompt behind it.
Original prompt
<inputs> Ask me for: 1. Product specs & BOM: exact millimeter dimensions and mesh parts (e.g. hex-lug outsole, 32/22 mm midsole, knit upper, heel counter, 12 eyelets, oval laces). 2. 3 colorways as calibrated hex codes (e.g. CHALK #F2EEE7, CINDER #2B2B2F, FLARE #D8322A) and typography specs. 3. Audio mood: tempo (150 BPM hype beat in D minor) and mechanical sound triggers for the Web Audio API. </inputs> <direction> High-end commercial product shot. 15.0s, 900 frames, 1080x1350 (4:5 vertical) at 60 fps. One HTML file using Three.js 0.160. One camera take, FOV 28, zero cuts: 40° orbit during explosion, push-in macro on the lacing, turntable during colorway sweeps, low angle for the drop. Studio lighting: cyclorama matching colorway tone, softbox reflections, 45° key light, 2 rim strips, contact shadows, highlight bloom, 1.5% grain. Soundtrack is 100% synthesized procedural code via Web Audio API (no audio files or samples). Every mechanical hit lands exactly 1 frame after visual contact. Banned: Loafers/blob geometry, bouncy easing, flat uncalibrated lighting, CSS transitions, template cuts, external 3D asset downloads (.gltf/.obj), pre-recorded samples. </direction> <structure> 150 BPM, 15 seconds, 900 frames (an action on every beat): 0.0s: Frame 0 starts mid-explosion. Parts already flying apart along a vertical axis (no intro fade). 0.4–1.6s: 2px leader lines and labels tick in on the beat: OUTSOLE, MIDSOLE, UPPER, HEEL COUNTER. 3.2s: Parts snap together bottom-up every 0.2s (damping 0.5). 4.8s: Laces thread criss-cross through 12 eyelets along a spline (0.2s per eyelet), tie a bow, and cinch at 7.2s. 8.0s & 9.6s: A sharp vertical light band sweeps across the frame; behind it, the shoe flips colorways: CHALK → CINDER → FLARE. 11.2s: Pedestal rises; shoe drops and lands at 12.0s with a volumetric dust puff. 12.8–15.0s: End card reveals logo, model name, and drop date; 808 sub rings out into the loop. </structure> <build> 1. Single HTML file. Compute every mesh position and material deterministically via window.renderAt(t). Support ?t= query param to freeze and inspect any frame in Chrome. 2. Build meshes to real-world measurements: millimeters, counts, and bevels. Avoid adjectives so Opus generates clean CAD-like geometry instead of blobs. 3. Calibrate studio lighting using an inverse tone curve so lit materials measure their exact target hex codes under the softbox. 4. Synthesize 150 BPM audio (kick, 808 sub, snaps, lace zips, whooshes) via Web Audio API at 48 kHz stereo. High-pass at 40 Hz and keep low-end energy under control for phone speakers. 5. Render in headless Chrome or Remotion Agent Skills at 2x resolution, blend 4 to 24 subframes per frame for hardware motion blur, and encode to 60 fps H.264. </build> <gotchas> Never start with a logo fade-in; hook the viewer by opening 0.1s into the explosion so frame 0 is pure motion. Keep the outsole anchored as the physical base so components stack strictly bottom-up without clipping. Offset audio transients by exactly +1 frame (+16ms) after visual collision for crisp impact sync, and duck the audio bed by 3.5 dB under clicks to prevent master limiter choking. </gotchas> <start> Ask me for the product bill-of-materials and 3 colorway hex codes, then output the 15-second frame-by-frame beat grid before writing any Three.js or Web Audio code. </start>
Video and prompt by vette. Original post ↗


