Ink Koi Pond
A koi pond seen from above, painted live as sumi-e ink wash on rice paper: eight koi flock with undulating spines and ink wakes, GPU-simulated ripples interfere, lily pads and lotus rock on the swell and petals fall. Tap the water to scatter the koi.
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 "Ink Koi Pond": a living koi pond seen from directly above, painted live in the style of Japanese sumi-e ink wash on rice paper. It should feel calm and meditative and be beautiful from the first frame. Single self-contained HTML file; Three.js and its addons from a CDN via an import map are fine; build everything procedurally (canvas textures are fine), no external models or image files. The pond (y up, the water surface at y = 0, the camera high above and tilted only about 9° from vertical): - Water: the whole frame is the pond. Warm cream rice paper shows through clear water, with soft cool grey-green washes and faint horizontal dry-brush streaks that gather towards the edges of the sheet. - Ripples: a GPU height-field simulation (ping-pong float render targets of about 512×512, a damped wave equation run at a fixed 120 steps per second) covering the visible water. Rings spread, cross, interfere and fade over a few seconds. Draw them like brushed rings: the slope facing away from the light darkens with ink, the lit slope lifts to paper white, and the ripples refract the koi and the pond floor below. - Ink: a second channel of the same simulation carries diluted sumi ink. It is advected by a slow curl-noise flow and by the ripple slopes, diffuses and fades. - Koi: eight koi, about 2.2 to 3.2 units long, of different varieties: kohaku, inazuma kohaku, taisho sanke, showa, tancho, yamabuki ogon (metallic gold), asagi (blue-grey net-scaled back, orange-red sides) and platinum ogon. - The body is a tube with an elliptical cross-section: a blunt rounded snout, the widest point about a third of the way back, a narrow tail stem. It bends along a spine that follows the head's path (a follow-the-leader chain with a bend limit), plus a travelling side-to-side wave that grows towards the tail. - The skin is painted per pixel onto a canvas: soft red and black patches with watercolour edges, scale reticulation, eyes, nostrils, the gill-cover line and a dark dorsal-fin line along the back. - Translucent fins with fine rays: a forked tail fin that flutters and lags behind the body, paddling pectoral fins (folded back when the koi flees) and small pelvic fins. Showa have black fin bases; sanke have black fin stripes. - Soft shading with a darker ink rim, a metallic sheen on the ogon, a slight fade with depth, and soft shadows of the bodies, fins and lily pads on the pond floor below. - Behaviour: loose flocking (separation, alignment, gentle cohesion), wandering, smooth turns with a limited turn rate, cruising that alternates with gliding, soft walls at the edges of the view, and areas kept clear under the title and the caption. Each koi drifts slowly between depths and leaves a trail of diluted ink from its tail. Now and then a koi rises and kisses the surface, making small rings. - Lily pads: nine notched pads in two clusters plus one on its own, painted with mottled grey-green washes, radiating darker veins and darker rims. They bob, tilt and rock on the ripples (sample the height field in the vertex shader). - Lotus: three open flowers (about 30 cupped petals in four rings, cream white blushing to deep pink at the tips with a fine carmine edge, a yellow-green seed pod with seed holes and a ring of golden stamens) and two closed buds, riding with the pads. - Petals: every few seconds a pink petal falls from above, spinning and swaying, with a faint shadow. It lands with a ring, floats and drifts, then fades. The nearest free koi swims up and nibbles at it, making tiny rings. The look: - Everything looks painted. In a post pass, wobble the image with paper noise, darken the pigment where it pools at edges, granulate it on a procedural rice-paper texture with fibres, bleed the edges softly and add a warm vignette. - The palette: cream paper, sumi ink, vermilion, gold, grey-green and lotus pink. Use ACES tone mapping, and choose the scene colours so that the paper comes out warm cream, not grey. No bloom. Never washed out or muddy. - The camera "breathes" slowly: a tiny drift of its position and aim. Interaction: - Tap or click the water: a large ripple and a drop of ink that blooms and curls. The nearby koi dart away and dive, then come back, curious. The wave pushes the lily pads aside, and they drift back; floating petals are pushed away. - Moving the pointer, or dragging a finger, trails small ripples. Interface: in the top-right corner, the vertical calligraphic title 蓮池遊鯉 in a brush font, with a red hanko seal under it (the two characters 墨鯉 cut white into a rough red rectangle, drawn on a canvas). In the bottom-left corner, a small caption: "Ink Koi Pond", one short line about what is happening (the koi drifting, a petal settling, a koi kissing the surface or tasting a petal, the koi scattering after your ripple and drifting back) and "tap the water". Everything starts automatically and is visibly moving from the first frame, without any interaction: warm the simulation up before the first frame, so that rings, wakes and bent spines are already there. The layout 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. - The page runs in a sandboxed iframe without same-origin access: do not use localStorage, sessionStorage or cookies. Cap the pixel ratio at 2. - 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 900 to 1,300 lines, compact and well structured.