Original prompt — Tested Claude Motion alternative — showreel from a single HTML file
by MotionPrompts (own run)
Prompt
Banned list ✓Beat grid ✓Build method ✓Self-review ✓
<direction>
An 8-second showreel that is literally one HTML file. A monospace badge in the corner reads "index.html — one file" throughout. Four scenes cut hard, one line each: ONE FILE. / NO BUILD STEP. / EVERY FRAME IS f(t) — then the end card, SINGLE-FILE SHOWREEL, with an accent rule and the line "ONE HTML FILE + ONE PROMPT — NO TEAM PLAN". Near-black background, white type, one orange accent.
Banned: glows, gradients, crossfades (this format cuts), external assets of any kind — if it is not in the file, it does not exist.
</direction>
<structure>
Scenes at 0s / 1.8s / 3.6s / 5.4s, hard cuts only. Each scene's line punches in with a short scale settle (1.07 → 1.0) so the cut has energy without a transition. The end card draws its accent rule after landing. Final frame holds.
</structure>
<build>
ONE self-contained HTML file, 1280x720 landscape: inline CSS, inline script, a paused GSAP timeline where every frame is a pure function of time (seek(t)), registered for frame-accurate rendering. Scene visibility is set on the timeline at exact cut times — no timers, no requestAnimationFrame loops.
</build>
<gotchas>
Hard cuts must be sets, not tweens: a 1-frame opacity tween still crossfades at render time. And the badge is a separate layer above the scenes, or the first cut takes it away.
</gotchas>
Before you finish: step through the timeline at five points and fix anything that overlaps, clips the frame, or drifts off the beat grid.
The whole showreel is one self-contained HTML file — no build step, no project scaffold — rendered frame-by-frame from a seek-driven timeline. The file badge stays on screen so nobody misses the point.
Run log
| Model | Claude (agent build) |
| Renderer / stack | Single-file HTML + GSAP (seek-driven) |
| Iterations to final | 1 |
| Render time | 20s (final render) |
| Format | 1280×720 · landscape |
| Published | 2026-10-25 |
What broke (and the fix)
- Nothing broke. One scare, recorded honestly: the render ran long on this machine (screenshot capture on software GL) and looked stalled at the compile stage — it was alive and completed. The scenes cut hard on their marks and the file badge survives every cut, as designed.
Related videos