Communitygithub.com

DigitalRavagers/Experiment

HyperFrames 컴포지션에 레지스트리 블록과 컴포넌트를 설치하고 연결합니다. hyperframes add 실행, 블록이나 컴포넌트 설치, 설치된 항목을 index.html에 연결, hyperframes.json 작업 시 사용합니다. add 명령어, 설치 위치, 블록 하위 컴포지션 연결, 컴포넌트 스니펫 병합, 레지스트리 검색, 그리고 업스트림 기여를 위한 새 블록/컴포넌트 작성(아이디어 → 스캐폴드 → 검증 → PR)을 다룹니다.

Experiment란 무엇인가요?

이 스킬은 HyperFrames 프레임워크의 레지스트리에서 제공하는 재사용 가능한 블록과 컴포넌트를 설치하고 연결하는 방법을 설명합니다. 블록은 독립적인 서브 컴포지션으로, 호스트 컴포지션에서 `data-composition-src` 속성을 통해 포함됩니다. 컴포넌트는 효과 스니펫으로, 직접 HTML에 붙여넣어 사용합니다. `hyperframes add` 명령어를 통해 설치하고, 블록 연결 시 `data-composition-id`, `data-start`, `data-track-index` 등의 필수 속성을 추가해야 합니다. 또한 `curl` 명령어로 레지스트리 매니페스트를 확인하거나, 새 블록/컴포넌트를 작성하여 업스트림에 기여하는 전체 워크플로우를 제공합니다. 이 스킬은 Claude Code, Cursor, Codex 등 명령줄에서 HyperFrames를 사용하는 모든 AI 에이전트에 유용합니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/DigitalRavagers/Experiment/tree/HEAD/.agents/skills/hyperframes-registry

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

HyperFrames 레지스트리

레지스트리는 hyperframes add <name> 명령어로 설치 가능한 재사용 가능한 블록과 컴포넌트를 제공합니다.

  • 블록 — 독립적인 서브 컴포지션 (자체 차원, 지속 시간, 타임라인). 호스트 컴포지션에서 data-composition-src 속성을 통해 포함됩니다.
  • 컴포넌트 — 효과 스니펫 (자체 차원 없음). 호스트 컴포지션의 HTML에 직접 붙여넣습니다.

빠른 참조

hyperframes add data-chart              # 블록 설치
hyperframes add grain-overlay           # 컴포넌트 설치
hyperframes add shimmer-sweep --dir .   # 특정 프로젝트 대상
hyperframes add data-chart --json       # 기계 판독 가능 출력
hyperframes add data-chart --no-clipboard  # 클립보드 건너뛰기 (CI/헤드리스)

설치 후 CLI는 작성된 파일과 호스트 컴포지션에 붙여넣을 스니펫을 출력합니다. 이 스니펫은 시작점이며, 블록을 연결할 때 data-composition-id (블록의 내부 컴포지션 ID와 일치해야 함), data-start, data-track-index 속성을 추가해야 합니다.

참고: hyperframes add는 블록과 컴포넌트에만 작동합니다. 예제의 경우 hyperframes init <dir> --example <name>을 대신 사용하세요.

설치 위치

블록은 기본적으로 compositions/<name>.html에 설치됩니다. 컴포넌트는 기본적으로 compositions/components/<name>.html에 설치됩니다.

이 경로는 hyperframes.json에서 설정할 수 있습니다:

{
  "registry": "https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry",
  "paths": {
    "blocks": "compositions",
    "components": "compositions/components",
    "assets": "assets"
  }
}

자세한 내용은 install-locations.md를 참조하세요.

블록 연결하기

블록은 독립적인 컴포지션입니다. 호스트 index.html에서 data-composition-src를 통해 포함하세요:

<div
  data-composition-id="data-chart"
  data-composition-src="compositions/data-chart.html"
  data-start="2"
  data-duration="15"
  data-track-index="1"
  data-width="1920"
  data-height="1080"
></div>

주요 속성:

  • data-composition-src — 블록 HTML 파일 경로
  • data-composition-id — 블록의 내부 ID와 일치해야 함
  • data-start — 호스트 타임라인에서 블록이 나타나는 시간 (초)
  • data-duration — 블록 재생 시간
  • data-width / data-height — 블록 캔버스 크기
  • data-track-index — 레이어 순서 (값이 높을수록 앞쪽)

자세한 내용은 wiring-blocks.md를 참조하세요.

컴포넌트 연결하기

컴포넌트는 스니펫입니다. 해당 HTML을 컴포지션의 마크업에, CSS를 스타일 블록에, JS를 스크립트에 붙여넣으세요:

  1. 설치된 파일 읽기 (예: compositions/components/grain-overlay.html)
  2. HTML 요소를 컴포지션의 <div data-composition-id="...">에 복사
  3. <style> 블록을 컴포지션의 스타일에 복사
  4. <script> 콘텐츠를 컴포지션의 스크립트(타임라인 코드 앞)에 복사
  5. 컴포넌트가 GSAP 타임라인 통합을 노출하는 경우 (스니펫의 주석 블록 참조), 해당 호출을 타임라인에 추가

자세한 내용은 wiring-components.md를 참조하세요.

검색

사용 가능한 항목 찾아보기:

# 레지스트리 매니페스트 읽기
curl -s https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry/registry.json

각 항목의 registry-item.json에는 이름, 유형, 제목, 설명, 태그, 차원(블록만), 지속 시간(블록만), 파일 목록이 포함됩니다.

유형 및 태그별 필터링에 대한 자세한 내용은 discovery.md를 참조하세요.

새 블록 또는 컴포넌트 기여하기

기존 항목을 설치하는 것이 아니라 새로운 레지스트리 항목(캡션 스타일, VFX 블록, 전환, 하단 써드, 또는 재사용 가능한 컴포넌트)을 작성하여 업스트림 PR로 제출하려면 contributing.md의 전체 아이디어 → 스캐폴드 → 빌드 → 검증 → 미리보기 → 배송 워크플로우를 따르세요. 시작 템플릿(캡션 / VFX / 컴포넌트 / registry-item.json)은 templates.md에서 복사하여 사용할 수 있습니다.

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

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.

DigitalRavagers/Experiment

Capture a general website/URL and turn it into a HyperFrames video (site tour, showcase, or social clip from the site's own visuals). Uses headless Chrome screenshots + brand assets. Use when intent is general — portfolio/blog/landing-page showcase or social clip from the site. NOT for: product/SaaS launch or promo (→ /product-launch-video, even from a URL); topic explainer with no site (→ /faceless-explainer); GitHub PR (→ /pr-to-video); adding captions to existing video (→ /embedded-captions); short unnarrated page-highlight motion graphic (→ /motion-graphics). Unclear launch-vs-general-site? Ask one question or start at /hyperframes.

관련 스킬