hyperframes-registry

Overview of hyperframes-registry skill

What hyperframes-registry does

The hyperframes-registry skill helps you install and wire reusable HyperFrames registry items with less guesswork than a generic prompt. It is built for the real job of turning hyperframes add <name> output into a working composition, whether you are adding a block, merging a component, or checking what exists in the registry.

Best-fit use cases

Use the hyperframes-registry skill when you need a practical hyperframes-registry guide for:

• installing a registry item into an existing project
• deciding whether an item is a block or a component
• wiring installed files into index.html
• reading hyperframes.json path mappings
• discovering registry items before you commit to one

What makes it different

The skill is strongest when the install path, file type, and integration steps matter. Blocks behave like standalone sub-compositions with their own dimensions and timeline; components are snippets that merge into the host composition. That distinction is the core decision point this hyperframes-registry skill clarifies before you edit files.

How to Use hyperframes-registry skill

Install and inspect the right files

For hyperframes-registry install, use the skill alongside the repository layout, not instead of it. Start with the item you are installing, then read:

• SKILL.md for the workflow
• references/discovery.md for registry lookup and manifest fields
• references/install-locations.md for default paths and hyperframes.json remapping
• references/wiring-blocks.md or references/wiring-components.md depending on item type
• examples/add-block.md and examples/add-component.md for end-to-end patterns

Turn a rough request into a good prompt

The best hyperframes-registry usage starts with a specific goal, not just a name. Strong input includes:

• the item name
• whether you want a block or component
• where it should live in the project
• whether you are wiring into an existing composition or starting fresh
• any path remapping in hyperframes.json

Example prompt shape:
Install data-chart into my HyperFrames project, wire it into index.html, and tell me which files and attributes need updating.

Workflow that avoids common mistakes

A reliable hyperframes-registry guide is:

1. Run hyperframes add <name> in the project.
2. Check the written files and the snippet the CLI prints.
3. Verify whether the item is a block or component.
4. Wire blocks with data-composition-src, data-start, data-duration, and data-track-index.
5. Merge components into HTML, CSS, and JS where the snippet says.
6. Update paths if your project overrides hyperframes.json#paths.

Practical quality tips

For better output, tell the skill what your composition already contains. For example, mention existing canvas size, timeline length, and whether you already have a host data-composition-id. That matters for hyperframes-registry for Design Implementation, because blocks must match the host layout and components must fit the current timeline and styles.

hyperframes-registry skill FAQ

Is this only for install tasks?

Mostly yes. The hyperframes-registry skill is aimed at install, discovery, and wiring decisions. If you only want a conceptual explanation of HyperFrames, a plain prompt is enough. If you need working file paths and integration steps, the skill is a better fit.

How is a block different from a component?

A block is a full composition with its own dimensions and duration, meant to be embedded with data-composition-src. A component is a snippet you paste into an existing composition. If you need independent timing or a separate canvas, choose a block. If you need an effect that merges into the current scene, choose a component.

Do beginners need to know the repo first?

No. The skill is beginner-friendly if you can recognize the goal: “install this item and wire it in.” The main beginner risk is skipping the wiring step after hyperframes add. The repo references reduce that risk by showing exactly where to look next.

When should I not use this skill?

Do not use hyperframes-registry if you are not working with the HyperFrames registry, if you are not installing anything, or if you already know the exact file edits and only need a tiny prompt rewrite. It is most useful when the install decision and integration details are still open.

How to Improve hyperframes-registry skill

Give the skill the missing constraints

The biggest quality lift comes from telling hyperframes-registry what the target composition expects. Include canvas size, timeline duration, install directory preferences, and whether the host project uses default compositions/ paths or remapped paths. That prevents mismatched paths and wiring assumptions.

Show the exact integration surface

For better hyperframes-registry usage, paste the relevant part of your host composition or describe it precisely:

• the index.html container
• existing data-composition-id
• current GSAP timeline start time
• any wrapper elements or layers already in use

This is especially important for block wiring, because placement and layer order affect whether the added item behaves correctly.

Iterate from the first output

If the first result is close but not ready, refine by asking for one of these:

• a corrected install path based on hyperframes.json
• a minimal wiring snippet only
• a block-vs-component recommendation for the same visual goal
• a merge plan that separates HTML, CSS, and JS steps

That feedback loop is the fastest way to improve hyperframes-registry results without overloading the initial prompt.