AI Video Creator · samples

Charalampos Raftopoulos

Video directed in Claude Opus 5.5 and built as code in HyperFrames: a written brief, a brand style sheet, every scene as editable HTML and GSAP, a still check before each render, and a native 16:9 and 9:16 cut with music.

raftopoulos.babis@gmail.com · Greece (UTC+2) · remote

1 · Process Street spec ad — “From chaos to proof”

One idea: the same tasks that pile up as chaos become one enforced workflow, and finished work becomes proof.

16:9 · 1920 × 1080 · 20 s · single link · download MP4
9:16 · 20 s · recomposed · single link · download MP4
How I made it: I wrote a detailed brief and a brand style sheet from process.st (real logo, Cabin font, colours, product screen and verbatim claims), had Claude Opus 5.5 write each scene as HTML and GSAP in HyperFrames, checked storyboard stills, directed the fixes (for example a weak first frame and a wrong task selection), and rendered a 16:9 cut and a recomposed 9:16 cut with music and sound effects on the beat.

Every on-screen claim is verbatim from process.st. Spec work for an application — not official Process Street content.

2 · How I made it

The real brief, style sheet, scene code, two real fixes and both final cuts — the workflow in 27 seconds.

16:9 · 1920 × 1080 · 27 s · single link · download MP4

3 · KAPOW! — one match, in panels

A different brand voice: the comic-book card game from my studio, Void Gaming. Real game screens, nine on-model fighters, cut on a 150 BPM grid.

9:16 · 1080 × 1920 · 16 s · single link · download MP4
How I made it: the same HyperFrames workflow, with the studio’s character sheets keeping every fighter on-model, the game’s real screens from its public page, and the studio’s own track (“Ink & Knuckles”, made with ACE-Step 1.5). Every cut and hit sits on the beat, measured at −15.6 LUFS.

My workflow in 5 lines

  1. Tools: Claude Opus 5.5 in Claude Code with HyperFrames, GSAP for motion, Blender for 3D inserts, licensed music and sound effects.
  2. References: one style and character sheet per brand (logo, colours, type, characters, allowed claims, “never change” rules), attached to every brief.
  3. Brief: a long written brief per video — the hook in the first 2 seconds, one idea, the scene list, the motion and the brand intent.
  4. Build: Opus 5.5 writes each scene as HTML code; I check storyboard stills, direct the fixes and re-render only what changed.
  5. Final: 16:9 plus a recomposed 9:16, music on both, captions on 9:16, delivered with the brief and a one-line note.