Communitygithub.com

DigitalRavagers/Experiment

Instale e conecte blocos e componentes do registro a composições HyperFrames. Use ao executar o comando `hyperframes add`, instalar um bloco ou componente, conectar um item instalado ao index.html ou trabalhar com o hyperframes.json. Abrange o comando add, locais de instalação, conexão de subcomposições de blocos, mesclagem de trechos de componentes, descoberta do registro e criação de um novo bloco ou componente para contribuir com o repositório upstream (ideia → esqueleto → validação → PR).

O que é Experiment?

Esta skill capacita agentes de IA a gerenciar o ecossistema de registro da HyperFrames, permitindo a instalação, conexão e contribuição de blocos e componentes reutilizáveis. Blocos são subcomposições independentes que possuem suas próprias dimensões, duração e linha do tempo, sendo incluídos via atributo `data-composition-src` em uma composição hospedeira. Componentes, por outro lado, são trechos de efeito sem dimensões próprias, colados diretamente no HTML da composição hospedeira. A skill fornece comandos CLI como `hyperframes add <nome>`, que instala o item, exibe os arquivos criados e um snippet sugerido para colagem. Para blocos, é necessário configurar atributos como `data-composition-id`, `data-start` e `data-track-index`. A descoberta de itens disponíveis é feita via consulta ao manifesto do registro (`registry.json`). Além disso, a skill orienta o fluxo completo de contribuição de novos itens ao repositório upstream, desde a idealização até o pull request, usando templates pré-definidos. Ela é útil para desenvolvedores que trabalham com HyperFrames em ambientes como Claude Code, Cursor ou Codex, automatizando tarefas repetitivas de integração e garantindo consistência nas composições.

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

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Registro HyperFrames

O registro fornece blocos e componentes reutilizáveis instaláveis via hyperframes add <nome>.

  • Blocos — subcomposições independentes (próprias dimensões, duração, linha do tempo). Incluídos via data-composition-src em uma composição hospedeira.
  • Componentes — trechos de efeito (sem dimensões próprias). Colados diretamente no HTML de uma composição hospedeira.

Referência rápida

hyperframes add data-chart              # instalar um bloco
hyperframes add grain-overlay           # instalar um componente
hyperframes add shimmer-sweep --dir .   # direcionar um projeto específico
hyperframes add data-chart --json       # saída legível por máquina
hyperframes add data-chart --no-clipboard  # pular área de transferência (CI/headless)

Após a instalação, a CLI imprime quais arquivos foram gravados e um snippet para colar em sua composição hospedeira. O snippet é um ponto de partida — você precisará adicionar os atributos data-composition-id (deve corresponder ao ID de composição interno do bloco), data-start e data-track-index ao conectar blocos.

Observação: hyperframes add funciona apenas para blocos e componentes. Para exemplos, use hyperframes init <dir> --example <nome>.

Locais de instalação

Blocos são instalados em compositions/<nome>.html por padrão. Componentes são instalados em compositions/components/<nome>.html por padrão.

Esses caminhos são configuráveis no hyperframes.json:

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

Consulte install-locations.md para detalhes completos.

Conectando blocos

Blocos são composições independentes — inclua-os via data-composition-src no seu index.html hospedeiro:

<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>

Atributos principais:

  • data-composition-src — caminho para o arquivo HTML do bloco
  • data-composition-id — deve corresponder ao ID interno do bloco
  • data-start — quando o bloco aparece na linha do tempo hospedeira (segundos)
  • data-duration — por quanto tempo o bloco é reproduzido
  • data-width / data-height — dimensões da tela do bloco
  • data-track-index — ordem das camadas (maior = à frente)

Consulte wiring-blocks.md para detalhes completos.

Conectando componentes

Componentes são trechos — cole seu HTML na marcação da sua composição, seu CSS no bloco de estilos e seu JS no script (se houver):

  1. Leia o arquivo instalado (ex.: compositions/components/grain-overlay.html)
  2. Copie os elementos HTML para dentro da <div data-composition-id="..."> da sua composição
  3. Copie o bloco <style> para os estilos da sua composição
  4. Copie qualquer conteúdo <script> para o script da sua composição (antes do código da linha do tempo)
  5. Se o componente expuser integração com a linha do tempo do GSAP (veja o bloco de comentário no snippet), adicione essas chamadas à sua linha do tempo

Consulte wiring-components.md para detalhes completos.

Descoberta

Navegue pelos itens disponíveis:

# Ler o manifesto do registro
curl -s https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry/registry.json

Cada registry-item.json contém: nome, tipo, título, descrição, tags, dimensões (apenas blocos), duração (apenas blocos) e lista de arquivos.

Consulte discovery.md para detalhes sobre filtragem por tipo e tags.

Contribuindo com um novo bloco ou componente

Para criar um NOVO item do registro (estilo de legenda, bloco VFX, transição, terço inferior ou um componente reutilizável) e enviá-lo como um PR para o repositório upstream — e não instalar um existente — siga o fluxo completo de ideia → esqueleto → construção → validação → pré-visualização → envio descrito em contributing.md. Modelos iniciais prontos para copiar e colar (legenda / VFX / componente / registry-item.json) estão em 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.

Habilidades Relacionadas