mengmengchen32

16 Product Film — Development skill for Claude Code

Development community

Claude Code skill: build and re-cut short product films from screen recordings + typographic title cards.

How to install 16 Product Film

This entry records only its repository, not the path inside it, so there is no exact command to give. Open mengmengchen32/16-product-film and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What 16 Product Film does

Claude Code skill: build and re-cut short product films from screen recordings + typographic title cards.

Alternatives in Development

Gallery — Build a static, shareable gallery from your fidelity reports — an index of score cards plus a permalink page ( 3.6k ★
Sanitize — Detect and redact PII from text files — 15 categories (SSNs, credit cards, API keys, etc.), zero dependencies 3.1k ★
Morning Debrief Analyzer — This prompt transcribes morning debrief audio recordings using OpenAI Whisper and analyzes the transcript to e 201 ★

README

product-film

A Claude Code skill for building and re-cutting short product films — the 60–120 second kind that alternates typographic title cards with screen recordings of a product working, and ends up on a homepage, a launch post, or YouTube.

It exists because that job looks simple and is mostly judgment, and because the judgment only becomes affordable if the film is a **build** rather than an **edit**. A reviewer will give you dozens of rounds of notes, most of them about pace, and will reverse themselves. Everything here follows from designing for that.

Install

git clone  ~/.claude/skills/product-film

Claude picks it up automatically. Invoke explicitly with `/product-film`, though it should trigger on its own for "cut this video down to 90 seconds", "turn this recording into something polished", "this looks blurry", or "add typing sounds to this".

What's in it

SKILL.md                      the craft: architecture, resolution, cut discipline,
                              pacing, sound, build gates
references/
  beat-timeline.md            typographic beats as a deterministic seekable timeline,
                              rendered frame by frame — and the gotchas that cost days
  typing-sfx.md               the full typing-SFX workflow, sample to final mux
scripts/
  frame_motion.py             find rest frames; check that cuts land on them
  cut_map.py                  segment ↔ film timecode, read from the concat list
  contact_sheet.py            tile several moments into one image to look at
  build_typing_bed.py         keystroke bed from a real recording, per a JSON spec
  scan_typeon.sh              locate the frame each type-on starts

The parts worth knowing before you read further

**Cut only on a frame that has come to rest.** Cutting away while the picture is still scrolling reads as disorienting — the eye is still tracking movement when the image is taken away. Measure it rather than eyeballing it,