data-* attributes, GSAP timeline registration, adapter registries, runtime-owned media playback — that generic web docs don’t cover. Install them before writing compositions and your agent produces valid HyperFrames HTML on the first try.
The skills split into three groups:
- Router — the entry skill that picks a workflow for any “make me a…” request — usually a video, but also a navigable deck (
/slideshow) or a composition port (/remotion-to-hyperframes). - Creation workflows — one per input shape (URL, PR, music track, captions, etc.). Each owns its task end-to-end: project setup, gated steps, and the final deliverable. Read by the router; you can also invoke directly if you already know which one fits.
- Domain skills — atomic capabilities (animation, media, CLI, registry) the workflows compose against; they never own the end-to-end task. Load one when you need that specific layer.
Install
1
Pick what to install (interactive picker)
hyperframes-* domain skills, and media-use) is listed under the “Core Skills” group, the on-demand creation workflows under “Other”. Keep --full-depth: it installs the current main. Without it, skills add fetches the skills.sh registry blob, which lags main by hours, so you may get an older copy of a skill. Works with Claude Code, Cursor, Gemini CLI, Codex CLI, GitHub Copilot CLI, and Google Antigravity.2
Or install everything at once (skip the picker)
3
Or install one skill at a time
/) — e.g. --skill hyperframes-animation. Useful when you want a single capability without the full set.4
Read /hyperframes first
Once installed, invoke
/hyperframes in your agent. It’s the capability map for everything below and routes “make me a…” intent — a video, a deck, or a composition port — to the right creation workflow based on your input.Keeping skills current
After the first install, skills stay lean and current on their own — nothing re-pulls the full set behind your back:- Core set — the
/hyperframesrouter, thehyperframes-*domain skills, and/media-use.npx hyperframes init(which every creation workflow runs when scaffolding) refreshes the core set plus anything else you already have installed. It never expands the install — workflow skills you haven’t used are not pulled — and re-runninginiton an up-to-date machine is a no-op. Offline (or rate-limited) it degrades gracefully and never hard-fails. - Workflow skills (and
/figma) — install on demand, when their workflow is first triggered. The/hyperframesrouter runsnpx hyperframes skills update <workflow>before entering a workflow, so the one it routes to is guaranteed present.
skills check reports workflow skills you haven’t installed as available on demand, not as a failure.
Router
The single entry point. Read/hyperframes before invoking anything else — it knows what’s available and which workflow fits your request.
Creation workflows
One workflow per input shape. The router (/hyperframes) picks one of these for you — but you can invoke them directly when you already know which fits.
Domain skills (loaded on demand)
Atomic capabilities the creation workflows compose against — pull one when you need that specific layer.Source of truth
The one-line “use when” for each skill comes from its ownSKILL.md frontmatter description: field in the hyperframes repo. The same catalog lives in the README’s ## Skills section and the repo CLAUDE.md; all three surfaces are kept in sync when a skill is added or renamed.
Next steps
Quickstart
Install skills, scaffold a project, and render your first video.
Claude Design
Produce a valid first draft in Claude Design, then refine in any AI coding agent.
GitHub Copilot CLI
Install and invoke HyperFrames skills from Copilot CLI in your terminal.
Google Antigravity
Use HyperFrames skills in Google Antigravity.