demo-video

demo-video

You need a finished, designed video of an app. This skill is the tested, batteries-included pipeline. It builds on HyperFrames (HTML→video) but adds the parts that are painful to rediscover: how to record the app yourself, this machine's ffmpeg workarounds, the exact edit recipes, the branded design system, and the traps that waste hours.

Nothing here is branded. The look is one design with swappable tokens; whose brand a video is in is a step, not an assumption — see Phase 0B.

🚦 The phases are grouped by topic, not by order of work

Read this before following anything below in sequence. The capture mechanics are documented first because they belong together, but capture is not the first thing you do:

The concept comes first:  what is this FOR?  →  the arc  →  PLAN.md (+ SCRIPT.md)  →  APPROVED
                          (that is the `video-plan` skill, not this one)             │
                                                                                        │
    ↓ only now does footage exist ──────────────────────────────────────────────────────┘
Phase 0 environment  →  0B brand  →  1A capture / 1B ingest  →  3 prep  →  4 compose
                                                            →  5 verify  →  6 render

Shooting first looks faster and is not: the arc is what changes under review, and every beat captured against an unagreed arc is re-captured. Phase 0 and 0B are the two things you may run early — they install tools and settle the palette. Everything in Phase 1 waits for an approved plan.

🚀 Trying it out — the fast path

🚨 The caller chooses this mode. You never do. You may OFFER it, in one question. You may not conclude it from circumstances, and these in particular are not consent:

• they attached or unpacked the skill package — that is how someone installs a tool, not a statement about what they want made with it;
• the request sounds exploratory, or came without a brief;
• it is the first thing they have asked for;
• you would find the fast path more convenient.