HyperFrames registry

HyperFrames registry helps find and integrate editable blocks and components for video scenes, transitions, and effects. Installed items become ordinary source files in the project, where they can be restyled, reduced, or changed. The workflow favors the largest reusable unit that fits the desired beat, then adapts that unit rather than writing an effect from scratch.

Blocks are scenes with their own timelines. Categories include transitions, overlays, lower thirds, title cards, kinetic typography, social and chat cards, code, charts, maps, 3D, shaders, and backgrounds. Components are snippets merged into an existing scene, including motion primitives, caption styles, camera moves, product-demo props, textures, particles, and other effects.

Use this skill when a HyperFrames project needs an existing visual building block that remains editable after installation. Search in English even when the video uses another language, because the catalog index is English. A query rejected for having no searchable words in another script does not establish a missing effect.

The default word-based search tier finds items that reuse the query's words. Optional on-device search ranks by meaning after a one-time download of about 33 MB; offer that download rather than enabling it silently. Search is local, sends nothing, and works offline from the cached manifest. Installation still requires a network connection, including for previously installed items.

If neither search tier finds a suitable effect, identify the gap before hand-building. Describe the desired motion rather than inventing an item name. Sending a search-miss report is an external message and needs a user request; telemetry consent by itself is insufficient.

Input is an English description of the desired beat, optionally narrowed by block or component type and tag. Search results identify the answering tier. Installation outputs the written files and a mount snippet:

npx hyperframes catalog --query "<what the beat should do, in English>" --json
npx hyperframes add <name> --json        # prints the written files and the mount snippet

Installing by tag adds every block with that tag, with dependencies installed first. Blocks go into the composition directory and mount through their source, matching composition identity, start time, and required duration. Components go into its components subdirectory; merge their markup, styles, and script into the scene, following timeline hook comments.

Keep installed identifier prefixes to prevent collisions. Each item retains its own variables, which can be set per mount and connected to brand color and font variables. Beat-synchronized blocks use detected hit times adjusted by the mount's start time. Project configuration determines installation locations.

A compatible HyperFrames CLI and its required dependencies provide search, installation, and beat analysis. Use the project's installed or explicitly selected version and review downloads before execution. Plugin-specific installation rules apply when the skill is part of a HyperFrames plugin. Apache-2.0 licensing is retained.

Default helper invocations disable telemetry, skill updating, and update checks. Preserve working version pins and unrelated files. Remote services, licensed media, publishing, paid generation, provider uploads, and recreated voices or avatars carry separate access, budget, rights, and consent requirements. Keep credentials in existing secret storage or ignored environment files. Verify actual visible output and accessibility before delivery rather than treating a recipe as proof that every environment works.