Communitygithub.com

1345AbhishekKumar/starter-supabase

Instalar e conectar blocos e componentes de registro em composições HyperFrames. Use ao executar hyperframes add, instalar um bloco ou componente, conectar um item instalado no index.html ou trabalhar com hyperframes.json. Abrange o comando add, locais de instalação, conexão de subcomposição de blocos, mesclagem de snippets de componentes, descoberta de registro e criação de um novo bloco ou componente para contribuir upstream (ideia → esboço → validação → PR).

O que é starter-supabase?

Esta habilidade fornece um guia completo para desenvolvedores que usam o ecossistema HyperFrames para gerenciar blocos e componentes reutilizáveis em composições de vídeo interativo. Ela cobre todo o ciclo de vida: desde a instalação de itens prontos via `hyperframes add`, até a conexão manual de blocos (via `data-composition-src`) e componentes (via snippets de HTML/CSS/JS) em arquivos `index.html`. A habilidade também explica como descobrir itens no registro público, configurar caminhos de instalação no `hyperframes.json` e como contribuir com novos blocos ou componentes seguindo um fluxo de PR estruturado (ideia → esboço → validação → PR). É útil para qualquer desenvolvedor que trabalhe com HyperFrames, seja iniciando um novo projeto, estendendo uma composição existente ou contribuindo para a comunidade.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/1345AbhishekKumar/starter-supabase/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, timeline). Incluídos via data-composition-src em uma composição hospedeira.
  • Componentes — snippets 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 .   # segmentar um projeto específico
hyperframes add data-chart --json       # saída legível por máquina
hyperframes add data-chart --no-clipboard  # ignorar área de transferência (CI/headless)

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

Nota: 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 em hyperframes.json:

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

Veja 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 timeline hospedeira (segundos)
  • data-duration — por quanto tempo o bloco é reproduzido
  • data-width / data-height — dimensões da tela do bloco
  • data-track-index — ordenação de camadas (maior = na frente)

Veja wiring-blocks.md para detalhes completos.

Conectando componentes

Componentes são snippets — cole seu HTML na marcação da sua composição, seu CSS no bloco de estilo 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 do <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 timeline)
  5. Se o componente expuser integração com timeline GSAP (veja o bloco de comentário no snippet), adicione essas chamadas à sua timeline

Veja wiring-components.md para detalhes completos.

Descoberta

Navegue pelos itens disponíveis:

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

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

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

Contribuindo com um novo bloco ou componente

Para criar um NOVO item de registro (estilo de legenda, bloco VFX, transição, terço inferior ou um componente reutilizável) e enviá-lo como um PR upstream — não instalar um existente — siga o fluxo completo de ideia → esboço → construção → validação → pré-visualização → envio em contributing.md. Modelos de início (legenda / VFX / componente / registry-item.json) estão em templates.md.

Individual skills in this repo

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

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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 (website-to-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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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 /website-to-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.

1345AbhishekKumar/starter-supabase

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.

1345AbhishekKumar/starter-supabase

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