---
name: showcase-reel
description: Turn a set of published project films into a 30 second, 16:9 showcase reel set on a photo mockup of a phone and a tablet. The phone shows a playlist of cards that scrolls and taps; the tablet plays each film in a large tile with a CRT switch-off and switch-on between clips, under a compact row of info cards. Includes an original, beat-matched music bed made in code and a two-beat title overlay. Use when someone wants a portfolio reel, a "my workflows" round-up, a device mockup video, a LinkedIn showcase of several projects, or says /showcase-reel.
---

# Showcase reel: Claude Code + a canvas + headless Chrome

A free skill by Chiang Ning (chiangning.net). It was built on P430, a 30 s reel of 8 of my AI visualisation workflows, from the Centre Pompidou isometric build to a timber gridshell in Revit. No video editor was opened. Every frame is drawn in code, and every rule below is something the project needed or something I said no to.

**What you get:** a 30 s, 1920 x 1080, 30 fps MP4 with music at -14 LUFS.
- A phone playlist that scrolls to each item and taps it, 0.12 s before the cut.
- A tablet that plays each film in a tile taking 80% of the screen, with a CRT switch-off (the picture collapses to a line, then a dot) and switch-on between clips.
- A compact row of cards under the video: title, bar meter, hashtag code, barcode, timecode, workflow and a big item number.
- A title that crossfades to a second beat (P430's says "Free download") on a bar line.
- An end card with your call to action.

**Who decides what.** Claude measures, builds, renders and checks. The person picks the films, the moment in each, the mockup photo, the look, the words on screen, and says no to each round. Show stills before every full render.

## 0. Inputs (ask only for what's missing)

1. **The films.** 8 is a good number for 30 s. Use the person's own finished films, at 1080p.
2. **A mockup photo** of a phone and a tablet with black screens, at least 1920 wide if possible. P430's was 1424 x 800 and it's the softest thing in the frame.
3. **The words:** a topic, a 2-beat title and a call to action, in the person's own wording.
4. **A UI reference,** if they have one. P430 went through a Winamp look, an LCD terminal and a yellow HUD before the person picked a card UI. Ask early.

## 1. Measure the screens

Read the photo's dark pixels to find each screen's bounds, then scale to 1920 x 1080. Keep the photo's own status bars and home icons and draw between them. If the tablet runs off the edge of the photo, let the UI run off too. It reads as real.

## 2. Pick the moments

Make a contact sheet: 5 stills from each film at 15, 35, 55, 75 and 92%. Pick a 4.5 s window from each that shows the result, not the start. Then cut them with `prep_clips.sh` at the video tile's exact size and 30 fps, so nothing gets upscaled.

- Screen recordings of Revit or Archicad: crop to the model viewport.
- Films with a caption burned into a corner: crop it off, or it fights your overlay.
- Pass `-nostdin` to ffmpeg inside a `while read` loop, or it eats the list.

## 3. The timeline

0.5 s intro, then 3.3 s per item (0.3 s switch-on and 3 s of film), then a 3.1 s end card: 30.0 s for 8 items. The film starts 0.75 s into each clip.

## 4. Draw it

1 canvas, 1 `renderFrame(t)` that depends only on `t`, so the live preview and the capture are the same frames.

- **Phone:** cards that scroll the next item to the middle 0.8 s before its cut, then a tap ring. The lit card takes its own colour.
- **Tablet:** the video tile first. Size it from the screen, about 80% of the visible area, at 16:9.
- **CRT switch:** for the last 0.22 s of each clip the picture squashes to a bright line, then a dot. The next one opens from a line with a white flash that fades. Keep scanlines faint. No TV static (the person found it noisy).
- **Type:** 1 sans for everything readable. Size the big title to fit its card.
- **Copyright or credit line** in small type, bottom right, if the person needs one.

## 5. The music

`music.py` writes an original bed with numpy: pad, pulse arpeggio, soft bass, drums, a sweep for each CRT switch-off, a thump for each switch-on and a click for each tap. Set the tempo so 1 item is a whole number of bars (3.3 s = 2 bars at 145.45 bpm), and every cut lands on the beat. Mux with `loudnorm=I=-14:TP=-1.5`.

## 6. Render and check

- `node capture.js stills /tmp/out 2.5 13.6 28.6`: check a playing frame, a switch and the end card every round.
- `node capture.js film /tmp/reel.mp4 30`: about 3 minutes for 900 frames on an M4.
- Render to a local folder and copy the file across. ffmpeg writing straight into a synced OneDrive folder timed out once.
- Before handing it over, look at 4 frames from the final file: the intro, a switch, a playing clip and the end card. Measure the loudness. Say plainly that nobody has listened to the music yet if that's true.
