Keep the edit repeatable
Update a beat after the UI changes instead of reconstructing the entire capture by hand.
Smart tool
TeaserKit
Change the interface. Re-shoot the same story.
For people producing repeatable product videos of web apps. TeaserKit writes the clicks, framing, captions and timing into a storyboard, then builds landscape, vertical and square outputs from that shared source.
One storyboard beats: browser steps, hold, caption, duration framing: region of interest for each aspect Build outputs landscape.mp4 vertical.mp4 square.mp4 no-audio copies and posters contact sheets and build record Review gate: inspect frames and watch the outputs before sharing.
Illustrative output layout for a fictional web app. No new film was produced for this marketing update.
Frame each shape deliberately
Give vertical and square their own regions of interest rather than relying on a crop of the landscape edit.
Review the whole output
Use validation, contact sheets, posters and build records to inspect timing, framing and accidental leaks.
The film
Change the interface. Re-shoot the same story.
In 71 seconds, a design change moves one button and Clix, the cursor in your product video, clicks where it used to be. TeaserKit writes the video down once as a storyboard, so you change one beat and rebuild landscape, vertical and square from the same story. Words on the deny list stop the recording if they appear, and you still watch every frame before you share. Captions are on the player; a transcript is below.
Read the transcript
This is Clix. Clix stars in your product video.
Then the design team moves one button.
Clix clicks where it used to be. All three versions of your video go stale.
TeaserKit writes the video down. Every click, caption and camera move lives in one storyboard.
The button moved. So you change one beat.
Build again. Landscape, vertical and square come from the same storyboard, each framed on its own.
Put private words on the deny list. If one appears on screen, recording stops.
And you still watch every frame before you share it.
On screen: Write the video down once.
TeaserKit. Change the interface. Re-shoot the same story.
The app in it, Acme Planner, is a fictional demo. The film shows how the tool behaves; it does not report results.
See the work take shape.
Illustrative output layout for a fictional web app. No new film was produced for this marketing update.
Write and validate the storyboard
Use the included fictional demo or scaffold your own project. Check beats, steps, captions and duration before recording.
Record and compose
Drive the live web app with Playwright, then render captions, camera moves, aspect-specific framing and the soundtrack.
Inspect before sharing
Read the contact sheets, watch the outputs and check for private text, spinners and broken layouts.
Fictional example
Fictional app re-shoot
The brief Inspect TeaserKit’s help and validate the included fictional demo storyboard. Explain the output shapes and the browser/ffmpeg prerequisites before proposing a build. Do not configure an AI provider, record a real product or generate a film during this first check.
Before
A manually recorded film requires a complete re-edit.
After applying the method
The storyboard changes the one beat and preserves the edit in three shapes.
The retained native capture/composition pipeline is independently useful to callers without Sizzle.
A clear job.
A useful stopping point.
Validate, record, compose or re-shoot a storyboard-driven app teaser.
Use it when
- A product video must be re-shot as the interface evolves.
- One story needs landscape, vertical and square versions.
- An agent should call a repeatable library rather than improvise a manual film edit.
Choose another route when
- A model requirement for deterministic recording and rendering.
- Calling a video finished before reviewing its frames and output.
Prepare
A filmed app needs a repeatable edit.
A storyboard with validated beats, steps and aspect-specific framing.
Build
A storyboard and capture environment are ready.
Captured takes, videos, posters and contact sheets.
Review
The footage needs quality or privacy inspection.
Contact-sheet findings; optional model review is advisory.
Read the canonical method
Use the native tool and its documented command interface.
Limits and prerequisites
- Deterministic validation and rendering do not require a model key; optional plan/explore/review capabilities can incur provider cost.
- Browser/ffmpeg prerequisites are explicit and are not installed as an unrequested side effect.
- No new film, live browser recording or paid provider call was performed in this local packaging baseline.
Your first useful run.
Validate the included fictional storyboard, then review prerequisites before your first full build.
This is a native tool or library. Install its package in an isolated environment, then use the documented command or protocol.
Start from the public source
git clone https://github.com/michaeljabbour/amplifier-smart-tool-teaserkit.git
cd amplifier-smart-tool-teaserkitpython3 -m venv .venv
.venv/bin/python -m pip install .
.venv/bin/teaserkit --helpUse the native package and command interface described in the installation guide. This capability does not require a portable skill.
- Python 3.11+, ffmpeg and Playwright Chromium are required for a full build.
- The deterministic library/CLI works without an AI provider. Optional plan, explore and review use the separately configured ai extra.
- Install the package first, inspect teaserkit doctor, then install any missing browser or renderer prerequisites deliberately.
- The shown virtual-environment commands use macOS/Linux paths; on Windows, use the corresponding .venv\Scripts executables.
Try this with your agent
Inspect TeaserKit’s help and validate the included fictional demo storyboard. Explain the output shapes and the browser/ffmpeg prerequisites before proposing a build. Do not configure an AI provider, record a real product or generate a film during this first check.Use after installing the documented native package. Read its help, supply an explicit task and inspect the result.
Keep the guide nearby
Read the guide · License · Changes · Release metadata · CONSOLIDATION · GUIDE · configuring ai
Know what you can rely on.
Deterministic and mocked checks plus installed storyboard validation passed. The full capture/render end-to-end check is separate; this update generated no new video.
Read the checks and their scope
- Native functional baseline — passed
45 deterministic/mocked tests (1 e2e skipped) and 2 fictional storyboard validation checks passed; no film or provider call.
- Source-specific acceptance — passed
45 deterministic/mocked tests (1 e2e skipped) and 2 fictional storyboard validation checks passed; no film or provider call.
- Live execution acceptance — not-run
No paid model call, real invitation, permission mutation, browser recording or film render was performed.
- Clean wheel installation — passed
All three wheels installed in a fresh Python 3.12 environment. Team Access help and TeaserKit no-AI storyboard validation passed; Imagen installed stdio smoke is recorded separately.
Source and conformance checks are separate from demonstrated benefit. Comparative effectiveness and outside-user outcomes are not established by this site.
Fictional examples explain the capability. Tests check the stated behavior. Outside-user outcomes need their own evidence.