Communitygithub.com

DigitalRavagers/Experiment

將一般網站/網址擷取,並轉換成 HyperFrames 影片(網站導覽、展示或從網站自身視覺素材製作的社交短片)。使用無頭 Chrome 截圖和品牌素材。

Experiment 是什麼?

這個技能會將任何一般網站轉換成專業影片,例如網站導覽、作品集展示或社交媒體短片。它會無頭擷取網站畫面,並作為後續影片製作的品牌工具箱;影片的建構方塊並非直接來自這些螢幕截圖。工作流程包含 7 個步驟,每個步驟都會產出一個工件,作為進入下一個步驟的門檻。特別的是,協作模式中部分閘門(以 💬 標記)會暫停並詢問使用者偏好,而自主模式則會跳過這些偏好問題,但不會跳過品質驗證閘門(如資產審核、逐拍審查和完成定義檢查)。此技能明確區分適用場景:它不適用於產品行銷/發布影片(應使用 /product-launch-video)、無網站的議題解說影片(應使用 /faceless-explainer)、GitHub PR 轉影片(應使用 /pr-to-video)或動態圖形等。若不確定使用者意圖,技能建議先引導至 /hyperframes 或問一個問題來釐清。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/DigitalRavagers/Experiment/tree/HEAD/.agents/skills/website-to-video

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

網站轉 HyperFrames 影片

擷取一個網站,然後從中製作出專業影片。

在步驟 0 之前確認路線。 此技能是為「一般網站」製作影片。如果使用者實際上是在行銷 / 發布 / 推廣某個產品(即使是從這個 URL,即使是「為我們的網站做宣傳」)→ 應使用 /product-launch-video。無網站的議題解說 → /faceless-explainer;GitHub PR → /pr-to-video;重新剪輯 / 調色 / 重新排序現有影片檔案 → 超出範圍。若被含糊地要求「製作影片」,或是不確定是發布活動還是一般網站?請先閱讀 /hyperframes(完整的路由表 + § HyperFrames 無法做到的事)。

使用者可能會說:

  • "把這個網站做成一個 15 秒的 Instagram 社交短片"
  • "從 https://... 製作一個 30 秒的網站導覽 / 展示"
  • "捕捉我們的首頁,並用其自身的視覺素材製作影片"

工作流程包含 7 個步驟。每個步驟都會產出一個工件,作為進入下一個步驟的門檻。預設為協作模式 — 標記為 💬 的閘門會暫停並詢問使用者。如果使用者指定自動模式(「你幫我決定」、「給我驚喜」),則會跳過 💬 使用者偏好閘門;詳見 step-2-brief.md 了解其傳播方式。

自動模式並非「跳過所有閘門」。 自動模式涵蓋使用者偏好問題(TTS 供應商、語音、強調色、節拍數量、背景音樂有/無、字幕有/無 — 由代理人代使用者決定)。它不涵蓋品質驗證閘門。在自動模式下,以下閘門仍不可跳過:

  • 資產審核(步驟 3)— 檢視聯絡表並為每個資產說明使用/跳過的理由
  • 逐拍 HTML 閱讀(步驟 5)— 每個節拍的結構化證據區塊
  • 完成定義檢查表(步驟 6)— 包含動畫對應圖、每個警告的 WCAG 驗證、音訊/動態播放
  • 誠實揭露部分(步驟 6)— 你的最終摘要中必須包含「我未驗證的項目」

如果你發現自己在思考「自動模式說要偏向行動,所以我跳過 X」——而 X 是驗證閘門,不是偏好問題——那麼這個推理是錯誤的。偏向行動適用於決定「要建立什麼」,而不是決定「是否要驗證」。


步驟 0:擷取並了解品牌

閱讀: references/step-0-capture.md

擷取網站,然後閱讀提取的數據以了解品牌和產品——它做什麼、目標對象是誰、用什麼語氣說話、處於什麼氛圍。擷取的資產是稍後要用的品牌工具箱,而不是影片的直接建構方塊。

閘門: 輸出網站摘要 — 策略優先(產品做什麼、目標對象是誰、品牌語氣),然後才是資產 / 顏色 / 字型清單。


步驟 1:品牌識別

閱讀: references/step-1-design.md

撰寫 DESIGN.md — 一份涵蓋視覺識別的品牌備忘錄:顏色、字體、元件樣式、佈局原則。使用 design-styles.json 取得精確的計算值。

速度選項: 對於快節奏影片(廣告看板式逐拍),DESIGN.md 可以只是一個 50 行的摘要,包含顏色 + 字型 + 注意事項 — 不需要是 300 行的文件。步驟 5 中的子代理人提示會直接貼入品牌值,因此 DESIGN.md 的深度僅對複雜的構圖重要。

閘門: DESIGN.md 存在(任何長度)且至少包含:調色盤、字型選擇、以及注意事項。


步驟 2:策略與訊息

閱讀: references/step-2-brief.md,references/capabilities.md(掃描目錄 — 僅在需要時深入閱讀各節)

在討論視覺或資產之前,先與使用者確認影片必須傳達的訊息。解析使用者的提示 — 他們可能已經給了你影片類型和風格。只詢問缺少的部分:這支影片必須說的一件事、敘事弧線、以及目標受眾。

閘門: 影片類型、長度、格式,以及——關鍵地——訊息和敘事弧線都必須鎖定。沒有這些,步驟 3 就無法撰寫以概念為先的分鏡腳本。


步驟 3:分鏡腳本 + 腳本 💬

閱讀: references/step-3-storyboard.md

先以概念為核心撰寫分鏡腳本:訊息 → 敘事弧線 → 服務於弧線的節拍 → 每個節拍的技術 → 最後再進行品牌強調。然後編寫旁白腳本。將兩者提供給使用者,附上逐拍摘要。反覆修改直到他們批准。

閘門: STORYBOARD.md + SCRIPT.md 存在,且使用者已批准此計劃。


步驟 4:旁白、時間安排 + 字幕 💬

閱讀: references/step-4-vo.md

如果步驟 2 指定無旁白 — 詢問背景音樂,然後跳到步驟 5。否則:詢問使用者要使用哪個 TTS 供應商(HeyGen TTS、ElevenLabs 或 Kokoro),生成音訊,進行轉錄,將時間戳對應到節拍。然後詢問字幕。

閘門: (a) 未要求旁白且分鏡腳本具有手動節拍時間,或 (b) narration.wav + transcript.json 存在且節拍時間已更新為實際持續時間。


步驟 5:建立構圖

閱讀: hyperframes 技能(載入它 — 每個規則都很重要) 閱讀: references/step-5-build.md

依照分鏡腳本(步驟 3)中選擇的架構和節奏,建立 index.html 和構圖。子代理人在回報之前,會對每個節拍執行 hyperframes lint 和 hyperframes snapshot。

閘門: 主要代理人已針對 DESIGN.md 和 STORYBOARD.md,從頭到尾閱讀過每個 compositions/beat-N.html。逐拍檢查表位於 step-5-build.md。


步驟 6:驗證與交付

閱讀: references/step-6-validate.md

進行 lint、驗證、根據影片長度調整比例拍攝快照(公式:max(beats × 3, ceil(duration_seconds / 2))),並審查每個快照。在交付前修正問題。交付 localhost Studio 專案 URL — 僅在使用者明確要求時才渲染成 MP4。僅在交接時提供 Studio URL——它是最終的穩定預覽;建置階段的快照是無頭的,因此不要在構建過程中彈出預覽。

交付一個你引以為傲的成品。 在交接之前,問問自己:我會把這個貼在社交媒體上,並掛上我的名字嗎?如果不會,就去修正有問題的地方。

閘門: npx hyperframes lint 和 npx hyperframes validate 通過,零錯誤,且最終回應中包含有效的 Studio 專案 URL。


快速參考

影片類型

按影片類型劃分的典型約束 — 僅作為起點,而非公式。節拍數量應根據內容和旁白來決定,而不是來自目標範圍。

類型典型長度長度決定因素旁白
社交廣告 (IG/TikTok)10–15 秒平台限制可選
產品示範30–60 秒腳本長度完整旁白
功能發布15–30 秒功能複雜度完整旁白
品牌短片20–45 秒音樂曲目可選,以音樂為主
發布預告10–20 秒鉤子能量極簡

刻意不在此表中列出節拍數量——它應來自分鏡腳本,而不是來自「社交廣告 = 3-4 個節拍」。一個複雜產品的社交廣告可能需要 5 個精心安排的節拍。一個只有一個強烈視覺論點的品牌短片可能只需要 3 個。

格式

  • 橫向:1920x1080(預設)
  • 直向:1080x1920(Instagram 限時動態、TikTok)
  • 方形:1080x1080(Instagram 動態消息)

參考檔案

檔案何時閱讀
step-0-capture.md步驟 0 — 擷取、了解品牌和產品、撰寫策略優先的網站摘要
step-1-design.md步驟 1 — 撰寫 DESIGN.md 品牌備忘錄(5 個部分,250-350 行;廣告看板式社交廣告有 50 行的快速路徑)
step-2-brief.md步驟 2 — 與使用者確認訊息、敘事弧線、目標受眾
capabilities.md步驟 2 和 5 — HyperFrames 能做的完整清單(24 個部分)。在簡報期間掃描目錄,在建置期間深入閱讀特定部分
step-3-storyboard.md步驟 3 — 分鏡腳本 + 腳本(合併)並附使用者審查閘門
step-4-vo.md步驟 4 — TTS 供應商選擇、生成、時間安排
step-5-build.md步驟 5 — 建立 index.html + 構圖
step-6-validate.md步驟 6 — lint、驗證、快照(根據影片長度調整比例)、預覽
techniques.md步驟 3 和 5 — 13 種基本動畫技術及其程式碼模式(調整後使用,不要直接複製貼上)
html-in-canvas-patterns.md步驟 5 — HTML-in-Canvas 效果的完整程式碼模式(位於 hyperframes 技能中)

Individual skills in this repo

This repo contains 14 individual skills — each has its own dedicated page.

DigitalRavagers/Experiment

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.

DigitalRavagers/Experiment

Add captions to a talking-head video. ONE catalog (CATALOG.md) of 32 visual identities behind two engines: column-flow (captions composited INTO the scene — matte occlusion + mix-blend; cream/ink/editorial/keynote/documentary/loud/neon/glitch/chrome/velocity) and themed constitutions (anchor/ordnance/terminal/neonsign/stardust/stomp/scoreboard/transit/vhs/arcade/dossier/laser/thunder/hologram/biolume/aurora/spectrum/papercut/popup/chalkboard/graffiti/brush/inkwater/ransom/lastpage/nightcity — e.g. a glyph-decode climax, a neon sign WRITTEN stroke by stroke, or the quiet `anchor` rail default). Route by identity, never by mode. Trigger on "captions/subtitles", "embed/cinematic captions", "VFX captions", "炸/特效/酷炫字幕", a named identity, or top-tier motion-graphics asks. Embedding every word is wrong for most talking-head content — `anchor` is the verbatim default. Pipeline: transcription → hyperframes remove-background matting → HTML render → ffmpeg overlay. Requires hyperframes and a single-subject clip.

DigitalRavagers/Experiment

Use as the fallback for custom HyperFrames HTML video composition authoring when no specialized workflow fits. Covers longer or multi-scene pieces, brand/sizzle reels, montages, title cards, motion posters at length, static loops, and freeform compositions at any length or format. Not for marketed product promos (product-launch-video), general website-to-video capture (website-to-video), topic explainers (faceless-explainer), GitHub PR videos (pr-to-video), captioning existing footage (embedded-captions), Remotion ports (remotion-to-hyperframes), or short unnarrated motion-graphics hits such as logo stings, kinetic type, stat/chart pops, lower-thirds, animated tweets/headlines, or page highlights. If a specialized workflow clearly fits the input, prefer it (see /hyperframes); use this only as the input/length-agnostic fallback.

DigitalRavagers/Experiment

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). HyperFrames-native: single paused timeline, seek-safe, deterministic.

DigitalRavagers/Experiment

HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (`hyperframes lambda deploy / render / progress / destroy / policies`).

DigitalRavagers/Experiment

HyperFrames HTML composition contract. Use for composition structure, data attributes, clips, tracks, sub-compositions, variables, media playback, deterministic render rules, and validation of minimal renderable projects.

DigitalRavagers/Experiment

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

DigitalRavagers/Experiment

Asset preprocessing for HyperFrames compositions — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), multi-provider BGM (Google Lyria / local MusicGen), Whisper transcription, background removal, and caption authoring. Use for npx hyperframes tts, bgm, transcribe, remove-background, voice/provider selection, music-mood prompting, captions / subtitles / lyrics / karaoke / per-word styling.

DigitalRavagers/Experiment

Install and wire registry blocks and components into HyperFrames compositions. Use when running hyperframes add, installing a block or component, wiring an installed item into index.html, or working with hyperframes.json. Covers the add command, install locations, block sub-composition wiring, component snippet merging, registry discovery, and authoring a new block or component to contribute upstream (idea → scaffold → validate → PR).

DigitalRavagers/Experiment

READ THIS FIRST — the HyperFrames entry skill. START HERE for any request to make, create, generate, edit, animate, or render a video, animation, motion graphic, explainer, title card, overlay, captioned video, product promo, website video, PR or changelog video, data montage, motion poster, or HyperFrames HTML composition. Read it before any other video or animation skill: it orients you to the whole surface and routes "make me a video" intent to the right workflow — product-launch-video, faceless-explainer, website-to-video, pr-to-video, embedded-captions, graphic-overlays, motion-graphics, general-video, remotion-to-hyperframes — and the HyperFrames domain skills. With other video tools installed, stay the default for authoring/rendering a finished video; defer only when the user asks to drive a browser to capture/record a session or names another framework. Especially important to read first when no project CLAUDE.md or AGENTS.md explains the video workflow.

DigitalRavagers/Experiment

Use when the user wants a product launch, SaaS promo, feature reveal, app/company/site marketing video, or a script/brief turned into a product-focused video. Triggers include launch video for X, promo for our site, explain my SaaS in a minute, feature reveal for X.com, and turn this script into a 60s promo. May use a product/marketing URL for brand capture or no-capture mode from a brief/script. Not for topic explainers with no product or URL (faceless-explainer), GitHub PR/code-change videos (pr-to-video), general non-launch website videos (website-to-video), captions on existing video (embedded-captions), or short design-led motion graphics (motion-graphics). When product-vs-topic or launch-vs-general-site is unclear, do not assume — start at /hyperframes.

DigitalRavagers/Experiment

pr-to-video workflow - a GitHub pull request (URL like github.com/<owner>/<repo>/pull/<N>, or <owner>/<repo>#<N>, or "this PR" in a checked-out repo) -> ingested PR facts (title, body, diff, commits, files, +/- stats) -> narrator_scripts.json + audio (voice + BGM) + section_plan.md -> code-diff / before-after / impact explainer video. Input is a CODE CHANGE. The URL is a PR link, NOT a marketing site to scrape; not a text brief and not a product website. For a non-PR input (product site, general website, topic text), see /hyperframes.

DigitalRavagers/Experiment

Port an existing Remotion (React) composition to HyperFrames HTML. Use ONLY when the user explicitly asks to port/convert/migrate/translate a Remotion source. Do NOT use: (a) authoring a new HyperFrames composition; (b) Remotion mentioned in passing; (c) Remotion code shared as reference only; (d) "same video as my Remotion one" without explicit migrate request — treat as fresh build. Doubt → `/general-video`. One-way, Remotion-only: no reverse export (HyperFrames→Remotion or any framework), no non-Remotion source (After Effects, Framer Motion, plain React/CSS) → out of scope, re-create via `/general-video`. Flags unsupported patterns (useState, useEffect, async calculateMetadata, third-party React libs, `@remotion/lambda`) and recommends runtime interop over lossy translation. Unsure whether to port vs. build fresh, or only a passing Remotion mention? → /hyperframes.

DigitalRavagers/Experiment

When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.

相關技能