← ClaudeAtlas

product-videolisted

Create a short premium product video (Remotion + React/TypeScript) from software that already exists in the repo — launch video, landing-page hero, demo reel, feature announcement. Works for web apps, mobile apps, CLIs, APIs and SDKs, desktop apps, extensions and data products. Clarifies scope first, then derives everything on screen from the repo rather than inventing it. Use when asked to make a product video, demo video, launch video, feature video, or to "record a demo" of something in this repo, or on /product-video. Not for motion graphics with no source software.
quybquang/product-video · ★ 0 · Code & Development · score 70
Install: claude install-skill quybquang/product-video
# Product video Turn software that already exists in this repo into a short, premium product video. The output is not a screen recording by default. It is a composition that reproduces the product's real interface, driven by the product's real data, so it looks like the product and survives someone checking it. Works for any kind of software. What changes between a web app, a CLI, an SDK and a game is the *stage* and the kind of *evidence* — the method is the same. ## Two rules **1. Clarify before you build.** Four answers — placement, duration, audio, audience — decide the architecture. Guessing any of them means rebuilding. Guessing *audio* means re-timing every scene, because with narration the frame timing is derived from measured clip durations rather than chosen. **2. Derive, don't decorate.** Everything on screen — every figure, every string, every interface element — must come from the repo, from running the software, or from a source you can name. Invented evidence is worthless the moment someone asks where it came from, and it is usually *more* work, because one invented detail needs a whole consistent world built around it. That applies to more than numbers. A button that does not exist, an error message you wrote yourself, a response you typed instead of ran, a "before" you built to lose — all the same failure. If you cannot source it, cut the claim rather than the corner. And mark derived values where they live: a one-line comment naming the file and the