كيف تبني عرضا سينمائيا مذهلا بالذكاء الاصطناعي؟
文章目录
部分视频或图片暂未收录,已在正文保留提示;需要时可查看原文。查看原文 ↗
إذا أردتم إنشاء عرضا بهذه الطريقة، استخدموا هذا الأمر، ثم كونوا الشرائح تدريجيا. الأمر هذا يطلب تكوين العارض، مع الأسلوب العرض.
Open an AI coding assistant that can create files and run commands on your computer (for example Claude Code) in a new, empty folder.
- انسخ الأمر التالي في Claude Code واستخدم النموذج Opus 5.5 أو حتى الجديد Fable 5.2. بعد ذلك اطلب منه إضافة الشرائح التي تود عرضها.
────────────────────
Build me a cinematic, clicker-driven web presentation
About my talk
-
Title and topic: [fill in]
-
Audience and occasion: [fill in]
-
Length: [for example, 20 minutes]
-
Look and mood: [for example, dark, cinematic and calm; default is dark and cinematic]
-
My computer: [Windows or Mac]
-
What I will supply: [images, a comic or storyboard, data, a script, or nothing yet]
-
First slides I want: [list them, or "none yet, build the tools first"]
What I want
I want a presentation that is a web page, not PowerPoint, and that I drive with a presentation clicker exactly as I would PowerPoint. It must not look like slides. It should feel like a film: one continuous world where things move, morph and arrive on each click, with very little text on screen. It should be fresh and beyond what people have seen before. Use everything you know about the best presentations and motion design ever made.
Besides the show itself, build the full set of presenting tools described below: a help screen, a presenter view with notes and a timer, an overview of every click, page numbers with jump-to-page, black and white screens, a key tester, a progress line, and a snapshot maker.
How we work
-
First explain, briefly and in plain language, how you will build it and what you need from me. Then wait for my go-ahead.
-
Build the engine and all the presenting tools first, with a quiet Start screen (nothing but the drifting background until the first click). If I have given you no slides yet, add one short page clearly labelled "Test" so I can try my clicker, and delete it when my first real slide goes in.
-
Then add slides gradually as I send material. Build only the slides I ask for. No filler, title, agenda or thank-you slides of your own; suggest them in chat instead.
-
When I send a screenshot and say something looks bad, redo that part properly. Don't nudge it.
Hard rules
-
It runs offline by double-clicking index.html (a file:// page) in Chrome or Edge. No server, no build step, no frameworks, no CDN links.Use classic <script> tags only. No ES modules, no fetch or XHR, and no WebGL textures loaded from image files: file:// blocks or taints all of them. Drawing images on a 2D canvas is fine. Download GSAP 3 (core only) once into vendor/ and the fonts into assets/fonts/ as .woff2 files. Everything else is hand-written HTML, CSS and JavaScript.
-
Never invent facts or statistics. Use what I give you, or research it and cite it: a small source line on the slide, the details in docs/sources.md, and the caveats in the speaker notes. Label illustrative charts "illustrative" and placeholder numbers "demo data".
-
Keep text minimal. One idea per click: a short kicker, a headline, big numbers. What I will say goes in the speaker notes, not on the screen.
-
Plain language in everything I read: help, notes, README.
The engine
-
A fixed 1920×1080 stage, centred and scaled to fit any screen.
-
The whole show is one paused GSAP master timeline. A beat is a point where the show stops and waits for a click. A scene is one page and can hold several beats.
-
Next plays the timeline forward to the next beat (tween the timeline's time, linear ease). Back plays it in reverse, about 1.8× faster. A click while something is animating finishes it instantly, then moves on. A jump of more than one beat is instant, hidden by a quick black flash.
-
Authoring API, used by js/deck.js:Deck.start(function (B) { ... }) builds the show. B.scene(title) starts a new page. B.beat(name, notes) marks a click stop; notes are my speaker notes for that moment. B.t() returns the current end of the timeline. Whatever is added to the timeline between two beats plays on that click.
-
Rules that keep Back and jumping correct:Set every initial state up front with gsap.set. On the master timeline use only .to() and .set(), never .from() or .fromTo(). Anything drawn by code (canvas, SVG, counters, typed text) is driven by watchers: the timeline tweens a plain state object, and Deck.watch(obj, drawFn) redraws whenever its values change, checked once per frame. No effect may depend on having been played forward. Each scene hides its own elements when it ends.
-
Helpers: Deck.split(el) (wraps words and characters for staggered text), Deck.typer(el) (a typewriter that never shifts the layout), Deck.decode(el) (random glyphs resolve into the text), Deck.counter(el, format) (animated numbers).
-
So the show can grow without one giant file: Deck.extras (functions in other js/scenes-*.js files that add scenes) and named Deck.slots hooks that deck.js calls at chosen points, so a scene file can insert pages mid-show.
-
Start-up: wait for fonts (5 seconds at most) and images (8 seconds at most) behind a small loader, then begin. A slow file must never block the show.
-
The current beat is kept in the URL hash, so refreshing reopens on the same beat.
-
index.html?lite uses far fewer particles, for weak laptops.
Controls: keyboard, clicker and mouse
A clicker behaves like a keyboard. It sends PageDown and PageUp or the arrow keys, often F5 or Esc for "start slideshow", and B or "." for "black screen". Map all of them.
-
→ ↓ PageDown Space N Enter, left-click: Next beat
-
← ↑ PageUp Backspace, right-click: Back
-
F, F5: Full screen on/off (F5 must not reload the page)
-
B or .: Black screen
-
W or ,: White screen
-
P: Open the presenter view
-
G or O: Overview
-
digits, then Enter: Jump to that page number
-
Home / End: First / last beat
-
H or ?: Help
-
D: Key tester on/off
-
L: Progress line on/off
-
Esc: Close any overlay
Also:
-
While the screen is black or white, the next press of Next, Back or a mouse click only brings the picture back. It does not change the slide.
-
Ignore key presses made with Ctrl, Alt or Cmd held down.
-
Suppress the right-click menu.
-
Hide the mouse pointer after two seconds without movement.
Presenting tools
-
Help (H or ?). An overlay with a table of every control above.
-
Page numbers. Each scene is one page. Numbers come from the order of the scenes, so they update by themselves when pages are added, removed or moved. The Start screen is page 0 and shows no number, so my first real page is page 1. Show the number small at the bottom right. Typing a number and pressing Enter jumps to that page.
-
Overview (G or O). A full-screen grid with a snapshot of every click, grouped by page, each group headed with its page number, title and number of clicks. The current click is highlighted. The arrow keys and the clicker move the selection, Enter or Space jumps there, a mouse click jumps there, and Esc closes it. A click with no snapshot yet shows its name instead, with a note saying how to refresh the snapshots.
-
How to build it: the two copies are iframes of index.html?mode=mirror and index.html?mode=preview. The windows talk through window.postMessage, which works on file://. The presenter window says hello every few seconds, so the link recovers if I reload the show. Embedded copies ignore the keyboard and mouse, hide the key tester and progress line, and use fewer particles.Presenter view (P). A second window, presenter.html, that I keep on my laptop screen while the show is full screen on the projector. It shows:a top bar with "click n / total", the page number, page title and click name, the time of day, and a timer that starts on my first click; Now: a live copy of what the audience sees, animating along with the show, with a progress bar under it; Next click: a second copy parked on the next beat, with its name; Speaker notes for the current click, in large type that I can read at arm's length; buttons for Back, Next, Black and Reset timer. The Next, Back and black-screen keys work in this window too and drive the show.
-
Black and white screens (B, W). A fade to black or white to pull attention back to me.
-
Key tester (D). A small box at the bottom right that shows the name of each key pressed and what it did ("next", "back", "not mapped"), so I can check what my clicker's buttons send. Off by default.
-
Progress line (L). A thin line along the bottom edge showing how far through I am. Off by default.
-
Snapshot maker. tools/make-thumbnails.js, with a double-click launcher for my computer, makes the overview's pictures. It drives a hidden Edge or Chrome window through the DevTools protocol using only what Node.js 22+ has built in, with no npm packages. It opens index.html?mode=thumb at 1920×1080, jumps to every beat, lets it settle, and saves a small JPEG of each to assets/thumbs/. It also writes assets/thumbs/thumbs.js, a script file that lists which beat each picture shows; it can't be JSON, because the page cannot fetch files. Match pictures to beats by name, so they survive pages being added.
-
Check scripts for you. In tools/dev/, the same hidden-browser approach for your own testing: one script that lists every page and beat and prints any console errors, and one that plays a click and saves frames part-way through, so you can look at your own animation before showing me.
The look
-
One living background. A single WebGL point cloud sits behind every slide: plain WebGL with no libraries, about 30,000 soft glowing dots, with fewer in lite mode and in the presenter copies. It never cuts. It morphs from one shape to the next, with each dot leaving at its own moment and swirling in flight.
-
Shapes that mean something. For each slide, the dots form something that relates to its subject: a 3D dotted model of the thing itself, a mathematical object, a network, a map. Build 3D models by scattering dots across surfaces in proportion to their area (boxes, cones, ellipsoids, surfaces of revolution, curves). No generic spheres or rings unless they mean something.
-
Dials the timeline can animate: position, scale, tilt, spin speed, a lock that stops the spin, a gentle sway, opacity, dot size, breathing noise, a wave, a burst outward, two colours, and how much the dots swirl during a morph. Write down the camera maths in a comment so labels can be pinned to the dots.
-
Composition. Put the cloud beside the text, not behind it, and dim it when the text needs attention.
-
Continuity. Scenes do not cut. Elements leave and arrive while the cloud morphs and the background gradient shifts colour. Add a faint film grain and a vignette over everything.
-
Type. Three bundled fonts: a tight display sans for headlines, an italic serif for emphasis, and a monospace for kickers, labels and source lines. Inter Tight, Instrument Serif and JetBrains Mono are good open-licence defaults.
-
Charts. Draw them in SVG so they animate: lines draw themselves, bars grow, numbers count up. Label the axes and give the source.
-
Bespoke moments. Where a slide deserves its own animation, use a canvas overlay driven by a watcher.
-
Smoothness. Animate transforms and opacity, and keep it at 60 frames a second on an ordinary laptop.
If I give you a comic or storyboard
-
Turn it into a motion comic: treat each page as a world and fly a virtual camera through it.
-
Dive into a panel, glide across the gutters, whip-pan, push through a window. Interpolate zoom on a logarithmic scale so it feels even.
-
Spotlight the active panel and dim the rest.
-
Pin effects to the art in the image's own pixel coordinates: rain, sparks, light blooms, flowing light, ripples, scans, camera shake.
-
One panel or moment per click, with my script as the speaker notes for that click.
-
Use my images as they are. If they are too small for deep zooms, tell me what size to export.
Files
-
index.html: the stage, the scenes' markup, the overlays
-
presenter.html: the presenter view
-
css/: styles
-
js/engine.js: beats, navigation, keys, overlays, presenter link
-
js/particles.js: the WebGL point cloud
-
js/comic.js: the motion-comic camera (only if I supply a comic)
-
js/deck.js: the choreography: every beat, transition and note
-
js/scenes-*.js: extra scene files
-
vendor/: GSAP
-
assets/fonts, assets/thumbs, assets/...: fonts, snapshots, my images
-
tools/: snapshot maker and its launcher; tools/dev/ check scripts
-
docs/sources.md: where every fact on the slides comes from
-
README.md: how to present, the controls table, what is on each page
-
CLAUDE.md or AGENTS.md: a briefing for a future AI session: how it is built and my rules
Before you tell me something is done
-
Load the show in the hidden browser and confirm there are no console errors.
-
Check that Back from every new beat restores the previous picture exactly, and that jumping straight to a beat gives the same picture as clicking through to it.
-
Look at frames from the middle of your animations, not only the end states.
-
Refresh the overview snapshots.
-
Update the README and the sources sheet.
-
Tell me plainly what you tested and what you could not, such as my real clicker or a projector.
沿着这个主题继续读
从一篇文章,找到相关的教程、经验和阅读路径。



