Guide

Release films

A short “what’s new” film of one release: the changed surfaces rebuilt from the source at the tag and shown changing in place.

A promo sells the product; a release film shows one release’s delta to people who mostly know the product already. It is the same engine, with the state before mattering, every claim bounded by a tag, and the film one episode of a series. Run /manovella:release-film, or choose the Release film recipe in the Studio, which writes a release brief with the version.

Is there a film in this release?

Only asked once you have asked for a film: nothing is proposed on its own initiative.

  • The list comes from the tag, never from memory: the log since the previous tag, the merged PRs, the draft release notes.
  • It qualifies when something a person sees or does differently ships: a new surface, a new control, a redesign, a new shortcut. Fixes, speed and internals do not; Claude says so in a line and stops.
  • At most three changes are featured. The rest go in the changelog roll, verbatim from the notes, or nowhere.
AskYou get
Release film for Acme 2.4 from the v2.4.0 tag: the three changes that show best, 16:9 plus a square cut.The changes read from the tag, a line on why each one shows well, one storyboard when the product already has a kit.
A what’s-new clip for 2.4 with only the new export sheet, 12 s, for the release notes.One featured change, between two version cards.
Three storyboards for 2.4, I’ll publish them in different places.A, B and C, each with its square cut, delivered side by side.

Claude asks in one message, each question with a default: the release and ref, the featured changes, the duration, the formats (a 16:9 master and a square cut as a second layout), the look, where it goes, and the music (none by default: release clips autoplay muted, so the text carries everything).

Sourced from the app, at the ref

  • The code is read at the ref, not the working tree (git show <ref>:<path>). View code gives the strings, symbols, spacing and colours; the project’s scripted screenshots give proportions. Never a capture with real data in it.
  • The before-state comes from the previous tag’s source: recreated from memory it is wrong in exactly the detail the release changed.
  • Every string on screen exists at the ref, menu items and keycap shortcuts included.
  • Headlines are the release notes’ benefit lines: a few words, and nothing the release does not do.
  • A change that ships off by default needs its switch on screen, or the film advertises something the viewer cannot find.

The shape of the film

  • Open and close on the version card: icon, name, “What’s new in X.Y”, the version in the accent colour. It is the first and the last frame, so the loop closes.
  • Change in place. The surface is shown as it was for a beat, then the change happens on it: the control lands in the toolbar, the list re-sorts, the panel grows a section. No before/after labels and no split screen; the transition is the explanation.
  • A new surface grows out of what opens it: the click, the menu item, the shortcut, pressed on keycaps in the headline slot.
  • One featured change, one headline, one interaction. The headline enters as the change lands.
  • The rest of the changelog as a short roll, “Also in X.Y”, three to five lines verbatim from the notes.
  • Close on the update path, clicked for real: the product’s own route to the new version.
  • Change in place is the format, not the only one: when the kit’s last film did it, the notes can open into the screens they describe, or the changed surface can turn in 3D depth. A major release can carry a long film in chapters beside the short clip.

Every click is seen

A release film is mostly clicks, and a click is a beat the viewer has to see land. The camera has arrived before the click, the cursor rests before it presses and stays through the press, and what a click opens never covers what was clicked. clickcheck.mjs measures all of it before the go, and Claude pulls a frame from the mp4 at every click time after the render.

The kit and the delivery

The first film of a product produces a kit: fonts, colour tokens, the icon as vector, the version card, the window chrome, the camera language and the look. Committed with the product, it lets the next release start from the kit: one storyboard, and only the content changes. A public repository keeps nothing unless you say so.

A release film ships with the release: the master mp4, a poster per aspect, the square cut if asked, chapter marks for a film of 30 seconds or more, and a YouTube title, description and tags beside it. Where each file goes is the project’s decision. The work folder is thrown away after the release, once the kit is safe (Delivery and cleanup).