Communitygithub.com

DigitalRavagers/Experiment

捕获一个通用网站/URL,并将其转化为 HyperFrames 视频(网站导览、展示或基于网站自身视觉的社交短片)。使用无头 Chrome 截图 + 品牌素材。适用于通用场景——作品集/博客/着陆页展示或源自网站的社交短片。

Experiment 是什么?

该技能用于将一个通用网站(portfolio、blog 或 landing page)的内容自动转化为高质量的宣传视频。它通过无头 Chrome 截取网站截图,并结合品牌资产(颜色、字体等)构建一个完整的 HyperFrames 项目。技能核心是一套包含 7 个严格步骤的工作流,每一步都会产生一个工件作为下一步的入口。技能支持协作模式和自主模式,但关键的质量验证步骤(如资产审核、逐小节 HTML 阅读、交付清单)即使在自主模式下也不可跳过。它特别适用于制作网站导览、展示视频或社交媒体短片,并在技能文档开篇就明确将其与其他视频类型(如产品发布视频、无网站主题解说、GitHub PR 视频等)的路径区分开来。用户应首先通过 `/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 社交短片”
  • “制作一个 30 秒的网站导览/展示视频,来自 https://...”
  • “捕获我们的主页,并基于其自身视觉元素构建一个视频”

工作流包含 7 个步骤。每一步都会产生一个工件,作为下一步的入口。默认情况下是协作模式——标记为 💬 的关口会停下来询问用户。如果用户指示了自主模式(“替我做决定”、“让我惊喜一下”),则跳过 💬 用户偏好问题;详情请参见 step-2-brief.md。

自主模式并不意味着“跳过所有关口”。 自主模式涵盖用户偏好问题(TTS 提供商、语音、颜色强调、节拍数、是否添加音乐、是否添加字幕——在这些问题上,Agent 代表用户做决定)。它不涵盖质量验证关口。在自主模式下,以下关口仍然不可跳过:

  • 资产审计(第 3 步)——查看联系表并为每个资产说明 USE/SKIP 的理由
  • 逐小节 HTML 阅读(第 5 步)——每个小节的结构化证据块
  • DoD 清单(第 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 步的子 Agent 提示会直接粘贴品牌值,因此 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 和构图。子 Agent 在报告之前,在每个小节上运行 hyperframes lint 和 hyperframes snapshot。

关口: 每个 compositions/beat-N.html 都由主 Agent 根据 DESIGN.md 和 STORYBOARD.md 从头到尾阅读过。逐小节检查清单位于 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 Stories,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.

相关技能