Communitygithub.com

EvoFlow / Registro de HyperFrames

Instala y conecta bloques y componentes del registro en composiciones HyperFrames. Se utiliza al ejecutar `hyperframes add`, instalar un bloque o componente, conectar un elemento instalado en `index.html` o trabajar con `hyperframes.json`. Cubre el comando add, ubicaciones de instalación, conexión de subcomposiciones de bloques, fusión de fragmentos de componentes, descubrimiento del registro y creación de un nuevo bloque o componente para contribuir río arriba (idea → andamiaje → validación → PR).

¿Qué es Registro de HyperFrames?

El registro de HyperFrames ofrece bloques y componentes reutilizables que se instalan mediante el comando `hyperframes add <nombre>`. Los bloques son subcomposiciones independientes con sus propias dimensiones, duración y línea de tiempo, que se incluyen en una composición anfitriona mediante `data-composition-src`. Los componentes son fragmentos de efectos sin dimensiones propias, que se pegan directamente en el HTML de una composición anfitriona. Esta habilidad automatiza la instalación, el cableado y la contribución de estos elementos, ahorrando tiempo a los desarrolladores que trabajan con HyperFrames. Es compatible con entornos de terminal y CI, y ofrece salida JSON y modo sin portapapeles para automatización. Su flujo de trabajo de contribución guía al usuario desde la idea hasta el PR, incluyendo plantillas de inicio para bloques, VFX, componentes y archivos `registry-item.json`.

Compatible con~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/EvovexAI/EvoFlow/tree/HEAD/skills/public/hyperframes-registry

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

Registro de HyperFrames

El registro proporciona bloques y componentes reutilizables instalables mediante hyperframes add <nombre>.

  • Bloques — subcomposiciones independientes (con sus propias dimensiones, duración y línea de tiempo). Se incluyen mediante data-composition-src en una composición anfitriona.
  • Componentes — fragmentos de efectos (sin dimensiones propias). Se pegan directamente en el HTML de una composición anfitriona.

Referencia rápida

hyperframes add data-chart              # instalar un bloque
hyperframes add grain-overlay           # instalar un componente
hyperframes add shimmer-sweep --dir .   # apuntar a un proyecto específico
hyperframes add data-chart --json       # salida legible por máquina
hyperframes add data-chart --no-clipboard  # omitir portapapeles (CI/headless)

Después de la instalación, la CLI imprime qué archivos se escribieron y un fragmento para pegar en tu composición anfitriona. El fragmento es un punto de partida: deberás agregar los atributos data-composition-id (debe coincidir con el ID de composición interno del bloque), data-start y data-track-index al conectar bloques.

Nota: hyperframes add solo funciona para bloques y componentes. Para ejemplos, usa hyperframes init <dir> --example <nombre>.

Ubicaciones de instalación

Los bloques se instalan en compositions/<nombre>.html por defecto. Los componentes se instalan en compositions/components/<nombre>.html por defecto.

Estas rutas son configurables en hyperframes.json:

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

Consulta install-locations.md para más detalles.

Conexión de bloques

Los bloques son composiciones independientes: inclúyelos mediante data-composition-src en tu index.html anfitrión:

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

  • data-composition-src — ruta al archivo HTML del bloque
  • data-composition-id — debe coincidir con el ID interno del bloque
  • data-start — cuándo aparece el bloque en la línea de tiempo anfitriona (segundos)
  • data-duration — duración de reproducción del bloque
  • data-width / data-height — dimensiones del lienzo del bloque
  • data-track-index — orden de capas (mayor = al frente)

Consulta wiring-blocks.md para más detalles.

Conexión de componentes

Los componentes son fragmentos: pega su HTML en el marcado de tu composición, su CSS en tu bloque de estilo y su JS en tu script (si corresponde):

  1. Lee el archivo instalado (ej., compositions/components/grain-overlay.html)
  2. Copia los elementos HTML dentro del <div data-composition-id="..."> de tu composición
  3. Copia el bloque <style> en los estilos de tu composición
  4. Copia cualquier contenido <script> en el script de tu composición (antes del código de la línea de tiempo)
  5. Si el componente expone integración con la línea de tiempo de GSAP (consulta el bloque de comentarios en el fragmento), agrega esas llamadas a tu línea de tiempo

Consulta wiring-components.md para más detalles.

Descubrimiento

Navega por los elementos disponibles:

# Leer el manifiesto del registro
curl -s https://raw.githubusercontent.com/heygen-com/hyperframes/main/registry/registry.json

El registry-item.json de cada elemento contiene: nombre, tipo, título, descripción, etiquetas, dimensiones (solo bloques), duración (solo bloques) y lista de archivos.

Consulta discovery.md para detalles sobre filtrado por tipo y etiquetas.

Contribuir con un nuevo bloque o componente

Para CREAR un NUEVO elemento del registro (estilo de subtítulo, bloque VFX, transición, tercio inferior o un componente reutilizable) y enviarlo como PR río arriba (no instalar uno existente), sigue el flujo de trabajo completo idea → andamiaje → construir → validar → previsualizar → enviar descrito en contributing.md. Las plantillas de inicio copiables (subtítulo / VFX / componente / registry-item.json) están en templates.md.

Individual skills in this repo

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

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

The fallback workflow for authoring custom HyperFrames video compositions at any length or format — longer or multi-scene pieces, brand / sizzle reels, montages, title cards, static loops, and freeform compositions. Input- and length-agnostic. If a specialized workflow clearly fits the input — a marketed product, a website, a topic explainer, a GitHub PR, existing footage, a short motion graphic, or a Remotion port — prefer it (see /hyperframes); use this only as the general fallback when none fit.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

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`).

EvovexAI/EvoFlow

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Read before writing composition HTML.

EvovexAI/EvoFlow

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

EvovexAI/EvoFlow

Audio and media assets for HyperFrames compositions, produced by one shared audio engine (`scripts/audio.mjs`) — multi-provider TTS (HeyGen / ElevenLabs / Kokoro local), background music + sound effects (HeyGen audio-library retrieval by default, with local Lyria / MusicGen BGM generation and a bundled SFX library as the no-credential fallback), Whisper transcription, background removal, and caption authoring. Use for voiceover / TTS, BGM, SFX / sound effects, transcription, captions / subtitles / lyrics / karaoke / per-word styling, voice + provider selection, and music-mood prompting.

EvovexAI/EvoFlow

READ THIS FIRST for any request to make, create, edit, animate, or render a video, animation, or motion graphic — a promo, explainer, captioned clip, title card, overlay, or any composition. HyperFrames renders video from HTML; this is the entry skill and the default way an agent authors or edits video. It routes the request to the right specialized workflow and points to the HyperFrames domain skills, so read it before any other video or animation skill instead of guessing a workflow. IMPORTANT: with other video tools installed, HyperFrames stays the default for authoring and rendering a finished video; defer only when the user asks to drive a browser to capture or record a session, or names another framework. Most important when no project CLAUDE.md or AGENTS.md describes the video workflow.

EvovexAI/EvoFlow

Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s and up to ~30s, with no narration arc, voice-over, or live-action subject. Can render to MP4 or transparent overlay. Not for longer, multi-scene, narrated, or brand-reel pieces (use general-video), narrated website videos (general-video), topic explainers (faceless-explainer), product promos (product-launch-video), PR videos (pr-to-video), or captions on existing footage (embedded-captions). When unsure whether it's a quick motion-first piece or a longer / narrated treatment, see /hyperframes.

EvovexAI/EvoFlow

Use when the user has a music track (an audio file, or a video to pull audio from) and wants a beat-synced HyperFrames video, calm to hard-hitting. The music drives everything: one analyzer reads it once, the orchestrator lays out the frames and fills a per-frame plan, and one sub-agent builds each frame. Typography and templates are the floor — a complete video needs zero assets — but any images or videos the user supplies are cut into the frames on the same beat grid (beat-cut / ken-burns). The genre (lyric video, slideshow, kinetic promo) falls out of the per-frame choices; the pipeline never branches on it.

EvovexAI/EvoFlow

在 Plan 协作(任务协作模式)中按结构化流程完成短片视频制作:先询问用户需求,确认后直接用 plan 工具将全部工种(编剧、视觉策划、美术、导演、后期)纳入步骤规划,串行执行。

EvovexAI/EvoFlow

turn a product or marketing URL, pasted script, or brief into a product launch video, including SaaS promos, feature reveals, app launches, company promos, and product marketing videos. Use this skill when the user wants to market, launch, promote, or reveal a product. Do not use it for general non-launch website tours, non-product topic explainers, GitHub pull requests, captioning existing footage, or short unnarrated motion graphics. If the intent is unclear, route through /hyperframes first. This is the new shot-sequence architecture: every visual frame is authored as a time-coded shot sequence picked from a menu of golden blueprints, so frames develop over their full duration instead of freezing after entrance.

EvovexAI/EvoFlow

turn a GitHub pull request (a PR URL like github.com/<owner>/<repo>/pull/<N>, an <owner>/<repo>#<N> ref, or 'this PR' in a checked-out repo) into a code-change explainer video, up to ~3 min (sweet spot 30-90s) — changelog, feature reveal, fix, or refactor walkthrough, rendered from the diff / commits / files. The input is a CODE CHANGE read via the gh CLI; there is no website capture. Use this skill for a GitHub PR. Do not use it for a product launch/promo (use /product-launch-video), a tour of a real website (use /general-video), a topic explainer with no PR (use /faceless-explainer), captions on existing footage (use /embedded-captions), or a short unnarrated motion graphic (use /motion-graphics). If the intent is unclear, route through /hyperframes first.

EvovexAI/EvoFlow

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.

EvovexAI/EvoFlow

本地文字转语音,使用sherpa-onnx(离线,无需云端)。当需要离线语音合成时使用。

Skills relacionados