hyperframes-registry

Run hyperframes add followed by the item name, such as hyperframes add data-chart for a block or hyperframes add grain-overlay for a component. Blocks install to compositions/ and components to compositions/components/ by default, configurable in hyperframes.json.

Run npx hyperframes catalog --query with an English description of the motion you need, for example "reveal a headline one line at a time". The query must be in English because the catalog is indexed in English, and --json output suits CI and agent workflows.

Add a div with data-composition-src pointing to the block file, plus data-composition-id matching the block's internal ID, data-start, data-duration, data-track-index, and data-width and data-height. The runtime seeks the block's timeline in sync with the host.

No. Only the registry manifest is cached, so catalog search and discovery work offline against the last fetched copy, but add fetches the item's actual files on every install and fails without network access.

A block is a standalone sub-composition with its own dimensions, duration, and timeline, included via data-composition-src. A component is an effect snippet with no own dimensions whose HTML, CSS, and JS you paste directly into a host composition.

Follow the clarify, scaffold, build, validate, preview, ship workflow: create the item directory with registry-item.json, pass hyperframes lint and check, regenerate registry.json, generate catalog docs, publish a preview, and open a PR.