video-shotcraft: Cinematic Product Video Production
A self-contained production skill library: 106 shot recipe cards (with demo source code and a dynamic motion gallery), one fully approved promo video template, reusable components and audio assets, and a six-stage workflow. The current focus is on web/desktop product promos, but the shot cards are universal motion design vocabulary — individual cards can be used for single shots in any video.
When to use this skill
Use when:
- Creating a cinematic product promo, product launch, or desktop/web application demo video.
- Naming or requesting the
Ink Presstemplate or reproducing the template promo effect. - Implementing a specific motion-design shot card (e.g.,
deck-deal-flyin,row-embed,spotlight-hero-card). - Needing 2.5D camera movements (PageCam), beat-synced video cuts with Remotion, and sound design.
Instructions
Step 1: Introduce the template and confirm the approach
Each time this skill is invoked, before starting any asset collection, storyboarding, or implementation, explain to the user:
- The
template/directory contains a fully approved 36.2-second product promo video template Ink Press: 1920×1080, 30fps, paper-ink-amber style, with 10 complete shots, 2.5D real-page camera moves, title cards, transitions, and pre-mixed cinematic SFX; just replace the target product's screenshots, copy, and brand information. - Using the template is the fastest and most quality-assured path; if the user wants a completely new visual language, proceed with a freeform creation process.
Explicitly ask: "Would you like to use this ready-made template for your video?" Inform the user they can browse the motion gallery at https://vincentwei1021.github.io/video-shotcraft/.
- User confirms use: First read
template/TEMPLATE.mdin full, then follow the template route. - User explicitly declines: Continue with Phase 0 of
references/pipeline.md, proceeding with freeform creation or single-shot route. - User is undecided: Stop and wait for a choice; do not default to the template or start production.
Exception:
- If the user specifically names the Ink Press template (e.g., "Make a promo for my product using the Ink Press template"), the template route is considered selected — directly read
template/TEMPLATE.mdand execute. - If the user explicitly specifies certain shot cards (e.g., "Use
deck-deal-flyinandrow-embedfor this video"), the route is considered selected — directly read the corresponding shot cards and the implementation source code indemos/<card-name>/.
Step 2: Choose one of three usage modes
- Full promo (template route): Read
template/TEMPLATE.md, follow the "product replacement guide" to swap assets shot-by-shot. - Full promo (freeform creation): Follow the six phases of
references/pipeline.md(starting with Phase 0's three startup questions). - Single shot / single effect: Select a card from
references/shots/, read the full card + implementation source indemos/<card-name>/, and adapt it to your target assets.
Step 3: When to read which file
| When | Read |
|---|---|
| Project kickoff | pipeline.md (Phase 0 three questions) |
| User has chosen BGM | music-beat-sync.md (analyze before storyboarding) |
| Template route | template/TEMPLATE.md (full) |
| Storyboard design | sequences/ scene templates; shots/ all frontmatter; selected cards read full content |
| Per-shot implementation | Full shot card + full implementation source in demos/<card-name>/ + corresponding components in assets/lib/ |
| Sound design | sound-design.md + assets/audio/ |
| Review | aesthetic-rules.md full checklist (executed by an independent sub-agent) |
Examples
Example 1: Template Route (Ink Press)
"Make a 30-second promo for my Desktop Product using the Ink Press template"
-> Automatically selects the template route, reads template/TEMPLATE.md, performs screenshot capture and asset replacement.
Example 2: Specified Shot Cards
"Create motion effects for my product demo referencing the deck-deal-flyin and row-embed shot cards"
-> Automatically selects the single-shot / combined-shot route, reads references/shots/ and demos/ source code for customized implementation.
Best practices
- Real screenshots: To replicate an existing page, always use real screenshots. Start by running a dev server and using a headless browser to capture 2x textures + layout.json.
- Product-native visual language: Extract tokens (fonts, sizes, colors, border radius) from the product/website design system — do not invent unrelated skins.
- Single motion per shot with breathing space: Each shot tells only one motion. Hold title cards / important visual beats for ≥1s after settling.
- Strict beat-syncing with strong BGM: Use
librosato analyze real BPM/time signature. Determine frames viabeatF(n), keeping cut error ≤3 frames. - Reference demo source code: Before using a shot card, read the tuned parameter truths and known workarounds in
demos/<card-name>/. - Deterministic rendering: Disable
Date.now()/Math.random(). Use fixed-seed pseudorandom.
References
template/TEMPLATE.md— Ink Press template structure and product replacement guidereferences/pipeline.md— Six-stage production pipeline specificationreferences/aesthetic-rules.md— Visual review and acceptance checklistreferences/music-beat-sync.md— Music rhythm analysis and beat-sync timeline calculationreferences/sound-design.md— SFX sound phrasing and audio asset pairing guide- https://vincentwei1021.github.io/video-shotcraft/ — Motion gallery and online gallery of 106 shot cards