Communitygithub.com

lifestyle-film

Make a tall lifestyle film from two photographs of the same physical subject and the product’s real phone screens. Move from the place to one thing in it, raise a live 3D phone already showing that thing, demonstrate one real task and its result, and close on the product’s identity. Use for launch or landing-page films for materials, plants, food, goods, rooms, stays and workshop tools.

Was ist lifestyle-film?

lifestyle-film is a Claude Code agent skill that make a tall lifestyle film from two photographs of the same physical subject and the product’s real phone screens. Move from the place to one thing in it, raise a live 3D phone already showing that thing, demonstrate one real task and its result, and close on the product’s identity. Use for launch or landing-page films for materials, plants, food, goods, rooms, stays and workshop tools.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/omnigami-ai/lifestyle-film/tree/HEAD/skills/lifestyle-film

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Lifestyle film

Make a tall (9:16) film of about 29 seconds: place → thing → phone → one task → readable result → identity. reference/ is a finished, editable example for Larchly, a fictional materials-board app using sample data. Adapt its machinery to the user's photographs, native screens, brand and words. Read style.md, ui-framing.md and critique.md first. The included instrumental song is made with AI.

Start or resume

Check Node 20.11+, ffmpeg, a Chrome-family browser with WebGL, and puppeteer-core. Python 3 with Pillow is needed for video review sheets. scripts/chrome.mjs finds Chrome; CHROME_PATH overrides it. Explain missing requirements before starting. No service account or paid rendering API is required.

Read the product URL, app/demo and supplied assets before asking for missing inputs. If several installed film skills fit an unnamed request, list them and ask which one to use. When this skill is named, proceed. For a revision, read PRODUCT.md, STORY.md and REVIEW.md and retain approved decisions.

Fit: the product helps someone work with a physical subject: materials, plants, food, goods, rooms, places to stay, tools in a workshop. It must run in a real phone layout. For a product with no meaningful physical world, such as a developer tool or a dashboard, say this film is a poor fit, stop and suggest a product film of its real screens instead. Do not add scenic photographs to imply a connection that does not exist.

Collect once, in one message, what the reachable product cannot answer:

  • A URL or runnable app/demo with its phone layout, one useful task and a sample account/data.
  • Two photographs of the same subject: a wide view of the place and a close view of one thing there. The app must actually show that thing. Prefer the user's own or licensed photographs. Otherwise use whichever image tool the user's agent has, guided by the product's own imagery as the material reference.
  • The product's mark, colors, licensed font, short benefit copy and closing line, plus anything to avoid.

For either photograph route: no people (a hand holding or using something is fine), no other brands' logos or text, no invented interface. Keep material, scale, color, light and physical context believable. Be honest about what is real: a planning study is not a finished installation. Record rights, generation and upscale routes in ASSETS.md. Use images large enough that the largest projected draw never enlarges their native pixels past 1.15×. Check the actual push and drift, not only the first frame. Fidelity upscaling needs inspection for invented detail. No registration or perspective match is needed between the two photos or between the close-up and the app: the joins use ordinary photos and a live phone.

Work outside this installed skill. SKILL_DIR is this file's directory:

mkdir lifestyle-film && cd lifestyle-film
cp -R "$SKILL_DIR/reference" reference
cp -R "$SKILL_DIR/reference" film
cp -R "$SKILL_DIR/scripts" scripts
cp -R "$SKILL_DIR/music" music
cp -R "$SKILL_DIR/tools" tools
rm -rf reference/out film/out
npm init -y
npm install -D 'puppeteer-core@^24'
node scripts/render.mjs reference --all --times key --sheet --out out/reference

Keep reference/ for comparison. In film/, retain the runtime, vendored Three.js, phone model and licenses; replace the photographs, capture sequences, font and lockup. Do not export Larchly assets in the user's film. Only tall is implemented. Do not promise square or wide exports.

1. The product and the story

Write PRODUCT.md like reference/PRODUCT.md: purpose, audience, voice, brand tokens, real routes/actions, one journey in order, which state proves each step, and what is still untrue at that point. Use sample data. Nothing is approved before the approval action, ordered before checkout, or installed because it was planned.

Write STORY.md like reference/STORY.md. One journey and one real task, no screen shown twice. Give each chapter its evidence, words, duration, incoming/outgoing move and reading hold. An editorial omission of setup is not a one-tap claim. Keep the reference's timing grid unless the real app needs longer; retain native waits and response timing first. Show the product note and story for approval before drawing. If the user explicitly requests unattended work, document evidence-based assumptions and continue.

2. Approve stills before motion

Make key stills for the place, close-up, phone/specification, task, result and close. Put them beside the reference's matching moments. Use the real UI unchanged, colors sampled from the product, its own font and exact mark. Show the photographs' relationship and every headline. Ask the user to approve this visual direction before animating, unless unattended. A later new tagline/card needs its own still first.

3. Capture the real product

Use scripts/screens.mjs; the plan format is in its header and example plans are under reference/capture/plans/. Run node scripts/centring.mjs <plan.json> before capturing. Use complete phone viewports, sample data and the real app at its supported width. The example has a 390×795 CSS viewport at 2×, 30 fps, with a captured 55 CSS-pixel system-chrome strip above it (780×1700 final raster). capture/plans/README.md explains the example's capture selection and reproducibility limits.

Record each action's target rectangle, approach, settle, held press, release, native response and lift. Capture the app's own animations frame by frame with animate steps, not just before/after stills. Play those frames at their recorded cadence. A state without animation swaps on the app's actual frame. Capture real DOM scrolls with their gestures; authored input paths are allowed, invented UI motion is not. Keep status time/signal/wifi/battery fixed on the display while app content moves below them.

Every press has the product's actual down state. The house fingertip helper eases from rest, selects a seeded point within the center 20% of the target, checks speed and keeps the entire disc inside the frame through approach, contact and lift. Capture plans include its helper and trusted-touch setup. Measure new control coordinates; never reuse Larchly's. Never redraw the UI, change native labels, crossfade captures, move a rectangle cut from a screenshot, or mask a fake confirmation into a card. If the app itself has a fault, report it; fix a user-owned app only within the authorized scope and recapture its real behavior.

4. Adapt the finished film

Edit film/film.js, not the shared runtime files. It separates tokens/words, named moves, source selection, phone/lens painting and window.template metadata.

Keep: openingPhoto's accelerating cut on motion, photoChapter/phonePose's already-live phone rise, normal phone attitude, refined concentric corners, studio/glass/lens, CPU pixel transfer, timing grid, headline anchor and stagger, reading holds and brandClose's coverage profile. Keep both joins generic.

Replace: JOIN_ASSETS photographs, C colors sampled from the product, FONT and its licensed file, DEFAULTS/fields words, lockup SVG, captures/manifests and every product-specific route, coordinate, source duration and claim. Set the document language to the user's product language; load a licensed font covering its glyphs and inspect its actual ink/line spacing. Do not leave English in a non-English film.

Adapt sourceAt, focus targets and nativeFramingAudit to the real task. Use whole captured viewports. If capture dimensions differ, update the native raster dimensions and status offset in screenPixels and screenUV together; retain aspect-fit and the concentric physical display. Never stretch UI to fit. prepareFrame prepares the bounded source window before synchronous seek; seek must throw for a missing frame rather than reuse an old one. Maintain keyTimes, cuts, shutters, uiChanges and honest self-checks at every new event. Every editable word belongs in template.fields, with realistic limits.

Keep slow drift through reading passages. Pan or pull back to expose content; do not use extreme tilt. No hard chapter swaps: use the two photographic/phone joins, the one-handset page excerpt and the closing coverage. The first photographic join has its deliberate opaque cut under motion blur. Do not hide it with registration, an in-between image or a dissolve. The phone is complete and already live when it enters.

5. Song and review render

tools/render.mjs uses the portable renderer, fits music/song.mp3 and music/song-stems/, and recreates the two-pass latency-compensated mix. tools/music-settings.json holds the sound clock/cues: keep it in sync with the film's duration and template.cues. The example is 110 BPM, downbeat .100 s, landing 24 s. The music begins on frame zero, keeps one uninterrupted song through the close, then rings out. Do not use a plain --audio render in its place: its limiter timing differs from this approved mix.

node tools/render.mjs film --all --video --blur 8 --draft --out out/review
node scripts/render.mjs film --all --draft --review --out out/motion
node scripts/render.mjs film --all --draft --check --check-fresh --stress --out out/check-draft

Review the MP4 and every native UI strip yourself, then give an independent reviewer the briefs in critique.md if available. Check 360 px readability, every headline's first/last three frames, all contacts, smooth encoded corners at 4×, both joins at full cadence/2× and the song onset. Score every rubric item 8+. Fix the worst three, repeating up to three rounds; then report remaining faults instead of claiming approval. Ask for motion approval before the final full render unless unattended.

6. Full render, checks and delivery

Render full quality once after approval (a GPU is strongly recommended; use one render at a time):

node tools/render.mjs film --all --video --blur 8 --out out/final
node scripts/render.mjs film --all --check --out out/check
node scripts/render.mjs film --all --check-fresh --out out/check-fresh
node scripts/render.mjs film --all --stress --out out/stress
node scripts/render.mjs film --all --poster 5.6 --every 0.5 --sheet --phone --out out/delivery
ffmpeg -i out/final/9x16.mp4 -af ebur128=peak=true -f null -

Read all three stress notes (default, long, short), not only the exit code. Actual text can still need visual fixes where the numerical test passes. Check true peak ≤−1 dBTP and audio ending with picture. Render on one machine/backend; different GPU/driver/font stacks can differ slightly. Local repeatability and fresh-page checks must pass on the chosen backend. Listen to the delivered file; a meter cannot approve how it sounds. Record unavailable visual/listening review explicitly.

Deliver the tall MP4, editable self-contained film, PRODUCT.md/STORY.md/ASSETS.md/REVIEW.md, poster, contact sheet and sharing caption, with licenses. Write out/delivery/caption.txt: one truthful sharing line and the product destination. Delete disposable raw frames once encoding and review are done; keep movies, review sheets and check reports. No network assets or maker mark in the film.

For a small revision use scripts/render.mjs film --draft --video --blur 8 --frames <a-b> --out out/patch and scripts/splice.mjs <review.mp4> <patch.mp4> --at <a> at the same quality; keep the original until the splice proves unchanged frames/audio. For sound-only revisions, node tools/render.mjs film --mix-only --out out/final remixes an existing full picture; --audio-only writes sound without rendering pixels.

Verwandte Skills