Skip to content

feat: use HyperFrames natively — skills for authoring + CLI for rendering #82

Description

@walliai666

While reading the codebase I noticed the notes already discuss calling
hyperframes render via child_process.spawn as the intended render path,
but it hasn't been implemented yet. Raising this as a feature request.

Benefits

  1. HTML generation via HF skillshyperframes-animation / hyperframes-creative
    encode the full authoring contract (data-* attributes, single paused timeline,
    seek-safe constraints) and 24+ validated animation recipes. Using them directly
    produces output that passes hyperframes lint by construction, which a
    hand-rolled prompt cannot guarantee.

  2. No need to reimplement or maintain the render pipeline — the current
    adapter reimplements font loading, GSAP pause/seek/resume, multi-composition
    inlining, duration probing, and ffmpeg transcoding. Calling hyperframes render
    returns all of that to upstream.

Is this on the roadmap? Would a PR be welcome?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions