_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

_{View prompt · GitHub · Watch preview · Website ↗ · Original post ↗}

💡 Pro Tip
imageSmoothingEnabled = false: Disable canvas interpolation and retain integer scaling and the pixel grid for crisp edges.

💡 Pro Tip
explainer: State the teaching or visualization purpose, then add audience, key conclusions and examples; verify facts and data.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
make the most realistic water scene it could, in WebGPU, with a floating camera.: Name the implementation or rendering tool and prepare its environment; a tool name alone is not a complete workflow.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
a voxel coral reef with schools of fish, a sunken shipwreck and light rays coming down: The public fragment gives a creative direction only; add subject motion, visual constraints and delivery format without assuming the full production process.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
1920x1080: Set aspect ratio or resolution before composing the scene to avoid cropping after export.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Use only: JavaScript, Playwright, and FFmpeg: Fix the production and export toolchain; prepare the product assets and portrait format specified in the prompt.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
One idea per shot: Give each shot one information point and follow the beat structure so product messaging and motion do not compete.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Every scene is made out of the previous one: Require each scene to transform out of the previous one instead of relying only on an Apple-style reference.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
avoid the border text or frames: Explicitly exclude borders and edge text so the reference ad's decorative elements are not copied wholesale.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
break them down into components/icons so we can animate those too: Split product screenshots into independently animated components instead of moving a flat screenshot as one slide.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
misty lake → hand mirror → back to start: Make the final scene return to the opening so the infinite zoom has a defined loop.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Do not stop at a storyboard, still images, or an implementation plan: Explicitly require a rendered and inspected result rather than accepting storyboards, stills or a plan as delivery.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
4 seasons passing outside a train window: Use the train window as a stable frame that connects the four seasons into one visual timeline.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
No interactivity: Specify a playback animation for the homepage so the 3D showcase does not expand into an unrelated interactive app.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
maps scroll progress to video.currentTime: Map scroll progress directly to video time rather than starting an independent playback timer.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
make this self-referential: Let the recursion explainer itself use a self-referential structure to make the concept concrete.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Pull some online data to see why it was hot and how it compares to other years: Require real data and year-to-year comparisons before visualization; check sources and dates.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Give the photon a personality: Personify the photon to give the audience a character to follow; verify the scientific explanation separately.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
empty glass to completed cocktail: Define the complete process from empty glass to finished cocktail with a checkable start and finish.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Before animating, study articles from the last three months: Research recent material before scripting the animation, then verify citations and conclusions.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
Don't feel the need to represent everything in the lyrics literally: Allow metaphor and cultural references so visuals interpret the lyrics rather than illustrating words mechanically.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
This is not a game and not combat-focused: Exclude combat and quests to focus the scene on exploration, architecture, atmosphere and discovery.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
pelican riding a bicycle: Use the same subject and action for comparison; add pedal and wheel coordination when reusing the short brief.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
No Three.js/Babylon.js, Canvas2D, external assets, video/GIF, or CSS-only deformation: Exclude prerecorded video and CSS deformation as substitutes for physics; check that meshes and simulation are implemented.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
take out key components of the star destroyer: Target specific enemy-ship components so combat objectives connect to the scene's scale.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
The player cannot directly attack: Limit the player's attack abilities so driving, evasion and induced collisions remain the core mechanics.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
1-on-1 card game like Hearthstone: Specify a one-on-one card battle, then add turn rules, costs and victory conditions missing from the public fragment.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
according to the dimension markings (mm) in the image: Use floor-plan dimensions and millimeter units to keep rooms and furniture proportional.

_{Original post ↗ · Prompt ↗}

💡 Pro Tip
while listening to the sound of rain: Frame the experience around rain ambience, then provide audio sources and interaction methods.