Chat launch
Explicit user instructions take priority over this workflow. Work only on authorized products and sample data. Do not request passwords, API keys, payment data, government identifiers, health records or other sensitive data. Explain missing local dependencies before installing them in the working project. Network access is for the authorized product and its licensed assets, plus the declared npm dependency; respect access controls. Render one job at a time and wait for completion. Keep publishing, sending and deployment outside this task.
If several skills could do this: when the request doesn't name this skill and your agent also has other omnigami skills that make the same kind of thing (other launch films, shots, decks or mockups), list them by name and ask which one the user wants before you start. If it's named, or it's the only one installed, go ahead.
For Japanese, Korean or Chinese product pages, keep the copy in that language and set the film’s lang to the page’s <html lang>; bundled Noto faces and phrase breaks handle the text.
You make a 23-second chat-style launch film for the user's product:
someone asks the product for something, it
works on it, the answer floods in as cards, the best one becomes the reply,
they click, and the button grows into the end card. One continuous take:
every scene is made from the one before it. You work by adapting a
finished film, not from a blank page: reference/ is a complete film for
Ostlery (a fictional company made for omnigami's examples: an assistant that
finds small stays and books them), with a measured layout and motion spec
(spec.md). Its screens are Ostlery's real app, captured; the film's own
shapes (the glow, the floods, the button, the outro) stand on top of them.
Keep its motion; change its content.
The film is tall (1080 × 1920). The phone's screen is the world the camera
moves through, in the app's CSS px (390 wide); the phone around it is a
photograph of an unbranded phone (assets/art/phone.png).
Read style.md before you start and critique.md before you judge.
Before you start
- Check the tools:
node -v(20 or later),ffmpeg -version, and a Chrome, Chromium, Edge or Brave install (scripts/chrome.mjsfinds it;CHROME_PATHoverrides). If something is missing, say how to install it and stop. - Ask once, in one message, for what the user hasn't given: the product's URL (or a public demo, supplied screenshots, or an explicitly authorized already-signed-in local browser), the one request a user would type into it, and the two closing lines. If they want no questions, decide from the site.
Steps
SKILL_DIR is the folder this file is in. Work in chat-launch-film/ in the current directory.
- Set up.
mkdir -p chat-launch-film && cp -R "$SKILL_DIR/reference" chat-launch-film/reference && cp -R "$SKILL_DIR/reference" chat-launch-film/film && cp -R "$SKILL_DIR/scripts" chat-launch-film/scripts && cp -R "$SKILL_DIR/music" chat-launch-film/music rm -rf chat-launch-film/reference/out chat-launch-film/film/out cd chat-launch-film && npm init -y >/dev/null && npm i -D 'puppeteer-core@^24'reference/stays untouched, for comparison. You editfilm/. - Learn the product.
node scripts/capture.mjs <url> capture, then look at every screenshot and readcapture/brand.json: its name, words, colors, logo and what it actually does. Then use it on a phone-sized window: ask it the request and follow what it really does, step by step. - Map the story onto the product. Never refuse a product and never force one into the reference's content: keep the film's moves and change what each one carries.
-
Find the thing that travels: the request, from the moment it's typed to the result the user acts on (Ostlery: the trip, then the stay it books).
-
Write the story in one sentence, from the product's real flow, and check it: every scene is a step the product really takes, in its order, once, and the end is the real result.
-
Swap a beat when the product doesn't have it; don't invent a feature for it. Each beat has stand-ins:
Beat Reference (Ostlery) Stand-ins the ask the request typed into the app's own composer a search box, a prompt, a form's main field thinking, one step a beat (beats 8–11) the search's four checks, each with its count the product's own progress: steps, sources read, a count, a status line; or one working state held over the beats the burst the six stays, captured one by one the product's result objects: rows, cards, files, matches the best the best fit flies back into its slot in the chat the result the product puts first the action "Book it" → "Booking" → "Booked" the product's real next step and its real states the close two lines, the mark, the wordmark same, in the product's words -
Say what changed. Write the sentence and the state list to
film/STATES.md(a table: time, state, what it shows, words on screen), and tell the user in a line which beats you swapped and why.
-
- Capture the product's real screens. Write
film/plans/mobile.jsonin the shape ofreference/plans/mobile.json(the format is at the top ofscripts/screens.mjs), at 390 × 844, scale 4: the start page (home); the composer after every keystroke of the request (ask-01…ask-NN, atypestep capturingaroundthe composer); the working states, one per beat (think-0…think-4; the reference reaches each with anevalthat shows that many checks done, the states the app passes through); the answer (results); each result card on its own (stay-0…stay-5, scrolling the row to each); and the action's states (booking,booked, at the answer's scroll). Recordrectsfor the composer and its send button, the message bubble, the working card and its spinner, the last count, the result cards, the reply lines, the actions and the button. Clear the composer before leaving the start page, as the app does on send. Then:The film reads its captures and rects fromnode scripts/screens.mjs film/plans/mobile.json film/assets/screens (printf 'window.SCREENS = '; cat film/assets/screens/screens.json; printf ';\n') > film/assets/screens/screens.jsscreens.js(a sandboxed preview can't fetch the JSON). Never draw a screen of the product for the film: what the viewer reads as the product is a capture of it. - Adapt
film/index.html. It is one file with labeled sections:DEFAULTSandFIELDS: the two outro lines and the tagline.KICKER,WORDMARK,DONE: the end card's small line, the name, and the done label the button grows with.- color and type:
PAPER,INK,EMBER(the accent: the floods, the dot, the mark),OK(the done state's color, if the product has one), and the product's two faces (Ostlery: Figtree and Newsreader, SIL Open Font License, inassets/fonts/).MARK: the product's mark asPath2Ds from its SVG. SCREEN,BAR,PHONE_SCREEN: the phone and its status bar; keep them.askScreen,thinkScreen,chatScreen,bookPill: each scene's screen, built from the captures and their rects.thinkScreengrows the working card a row at each toss and spins its spinner;chatScreenlets the reply rise line by line and the actions pop in;bookPilltakes the button through its states (its label leaves, the next rises; the done color fills out from the check).stripCards,drawStay: the result cards (fromstay-N), their burst, slide and lift;CARD_W,CARD_Hfrom the card captures.camKeys: where the camera looks in each scene and how close, in the world's CSS px: the composer, the working card, the chat before and after the pan, the push into the button. Keep the motion code as it is:T(the beats),SEND, the camera's times, the springs, the floods, the burst and slide, the fill, the cursor's times, everypress. Keep every text size of the film's own words (the table under "Type" instyle.md). If words don't fit, cut words; never shrink the type below it.
- Check stills against the reference.
It renders both films at one moment inside every state, the reference above yours. Look at it properly. Then run the quick test and the phone check:node scripts/compare.mjs reference film out/compare-9x16.png --size 9:16
The quick test fails if a word leaves the frame, overlaps another or falls under the size floor, with the words at their longest and at their shortest; its notes about crops the camera makes on purpose (the status bar's clock while it's close on the screen) are not failures. Look at every sheet it writes tonode scripts/render.mjs film --size 9:16 --stress node scripts/render.mjs film --size 9:16 --phoneout/stress/for what it can't measure: a word clipped by a card or a rounded corner, a frame that looks crowded or empty. Fix anything that failscritique.md, then compare again. Repeat until every score is 8 or more. - Check the motion on strips of consecutive frames from the MP4 (step 9), around every hand-off: the send (3.6–4.4), each toss (4.62, 5.08, 5.54, 6.0), the drop (7.3), the burst and slide (7.5–8.6), the card flying home (9.8–10.3), the click and its states (12.4–13.4), the fill (14.2–14.6) and the mark (16.4–18.0). Then check the breathing room at every beat (
style.md): nothing acted on the instant it appears, every result held a second. Then get a fresh judgement: if your agent can start a sub-agent without this session's memory, give itcritique.mdand the images, nothing else, and fix the worst problems it finds; otherwise rereadcritique.mdand score from the images alone, as a stranger would. - Check it's repeatable:
node scripts/render.mjs film --size 9:16 --checkmust pass. - Render.
This writesnode scripts/render.mjs film --size 9:16 --video --blur 4 --audio music/song.mp3 --bpm 130 --land 16.62 --sound --poster 8.4out/9x16.mp4(1080 × 1920): 60 fps, motion blur, the skill's own song and effects from omnigami's own sound kit, loudness about −14 LUFS, and a poster (out/9x16-poster.png). The song (music/song.mp3: bubbly, bright synth-pop at 130 BPM, the film's tempo) is fitted to the film bysong.mjs:--bpm 130gives it the tempo it was made at (its beat measures a little slow without it); it starts on a bar line and lands one hit on the first outro line (--land 16.62; move it with that line if you retime the outro), where its drums stop and the rest closes and fades (from its stems inmusic/song-stems/).--from <seconds>starts at another of its distinct 8-bar sections (the song is about two minutes long).--musicgives the synthesized 130 BPM score instead. For the user's own song, use--audio their.wavwithout--bpm(cleanest with its stems in atheir-stems/folder beside it); a song near 130 BPM fits the film's cuts, and--fromcan start it 16 beats before its drop. Run it in the foreground and wait for the file. - Write
chat-launch-film/README.md: what each file is, where to change a word, how to recapture the screens, and the render command. Also writeout/CAPTION.md: a post to share the film on X or LinkedIn, under 280 characters, in the product's own words, with its URL; no hashtags unless the user asks. - Report: the MP4, the poster, the caption, the story sentence and state list, which beats you swapped, the final scores, and the one change that would improve it most.
Rules
- Only what the product does. Every state is a capture of the product doing it, in its own words; the action is real; sample data only, no real customer data or real company names.
- A story that holds. One thing travels the whole film; every step is real, in the product's order, once; the end is the real result.
- Let each result land. Keep the reference's holds, and lengthen by whole beats rather than cut one: the request holds a second before it sends, the last step of the work a second before the drop, the best result a second before it flies, the reply is read before the actions, the cursor rests before its click, the done state holds a second, each closing line is read before the next.
- Keep the motion. Timing, camera, springs and floods come from the reference. If content doesn't fit, shorten the words before changing a box.
- Every click has a press state, and shapes change in one move (
style.md, Motion). - Keep the engine rules (
style.md):seek(t)paints from its arguments only; no clocks, noMath.random, no timers, no network; every file insidefilm/. - Only the user's brand. No other company's name, logo or UI: the phone is the reference's unbranded photograph, its status bar generic.
Files
reference/: the Ostlery film (index.html), its capture plan (plans/mobile.json) and captures (assets/screens/, withscreens.js), the unbranded phone (assets/art/phone.png), fonts (Figtree and Newsreader, SIL Open Font License),kit.js(springs, text fitting). Ostlery is a fictional company made for omnigami's examples.scripts/:capture.mjs(brand from a URL),screens.mjs(the product's real screens, from a plan),render.mjs(stills, strips, the quick test, checks, MP4s),compare.mjs(reference against yours),preview.mjs(a local preview that edits the words),music.mjs(the synthesized score),song.mjs(fits a supplied song) andsfx.mjs(effects from the kit insounds/),chrome.mjs.music/: the skill's song and its stems.style.md: the grammar, the states, the motion numbers, the banned list.critique.md: how to score and what to hunt for.spec.md: the layout, beat grid, type sizes and motion measurements.
This skill is omnigami's, © 2026 Auberon LLC. Use what it makes for anything, commercial work included, and change the skill for your own use; don't redistribute or sell the skill. Full terms: LICENSE.md
Phone display corners
Keep the backing mask inside the photograph's actual opening: its native 490 px width uses a 49 px mask radius (49 * screenWidth / 490). The original photograph supplies the final glass edge and bezel. A tighter independent mask exposes background through its transparent opening. Inspect all four corners in a complete device view.