Individual skill
HyperFrames
One-off semantic animations and animated explainers authored as HTML + GSAP on HyperFrames, directed by the meaning layer (MeaningMap then Direction, reviewed before anything animates) and rendered to MP4 through the sandboxed HyperFrames seam, with the ArtDirection quality loop before delivery. USE WHEN animation, animate this, motion graphics, animated explainer, content to video, make a short, generate a video about, launch video, product launch video, launch film, capability video, feature video, make a video of what we just added, promo video, ad creative video, landing-page hero video, AI video, video overlay, render video, programmatic video, hyperframes, remotion (retired). NOT FOR static images or diagrams, or animated technical diagram GIFs (Art TechnicalDiagrams, which renders through this seam), editing or tight-cutting recorded footage (the video pipeline skill), narrated essays or explainers of a post, idea or feature (the video-essay skill), or audio-only cleaning (AudioEditor).
LifeOS/install/skills/HyperFrames/SKILL.md
Source commit b7efec97d8c3885feee285bee468c35602fb0606
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 2, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 19,762
- Repository last updated
- Nov 5, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- augmentation Repository topic
- productivity Repository topic
- humans Repository topic
- ai-harness Repository topic
- intent-engineering Repository topic
- personal-ai Repository topic
- coding Repository topic
- lifeos Repository topic
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Intents/CapabilityVideo.mddoc · 6,829 bytesIntents/ContentToAnimation.mddoc · 6,241 bytesIntents/GeneratedContentVideo.mddoc · 6,750 bytesIntents/LaunchVideo.mddoc · 26,056 bytesIntents/SystemFilm.mddoc · 10,821 bytesReferences/LaunchFilmCraft.mddoc · 6,928 bytesReferences/MotionDesignPhilosophy.mddoc · 5,774 bytesReferences/MusicScore.mddoc · 1,872 bytesReferences/VoiceoverCleaning.mddoc · 2,299 bytesSKILL.mdcore · 13,574 bytesSKILL.mdcore · 13,574 bytesSetup.mddoc · 4,176 bytesTools/FilmStats.tsruns · 5,672 bytesTools/Scaffold.tsruns · 9,527 bytesTools/SystemFilm.help.mddoc · 5,416 bytesTools/SystemFilm.tsruns · 62,001 bytesTools/TextFit.tsruns · 75,849 bytesTools/Theme.tsruns · 7,064 bytesTools/WatchFilm.tsruns · 6,036 bytes
Read excerpt
# HyperFrames
Makes short animations the way Art makes images: from code, reproducibly, from what the content means. A composition is an HTML page with one paused GSAP timeline; HyperFrames seeks it frame by frame and encodes it. Every render goes through the shared seam `LIFEOS/TOOLS/HyperFrames`, which pins the version, turns telemetry off, sandboxes the network, checks the timeline is registered and moving, and remuxes the output without container metadata so the renderer's own name and version stamp does not travel with the file. It adds no AI-content label of its own; label AI-generated shorts wherever they are published.
Order is fixed: meaning, then direction, then motion. `LIFEOS/TOOLS/VideoMeaning` decomposes the source into a MeaningMap, directs every beat as a Direction with a written rationale, and a two-vendor review passes that plan before a single scene is authored. A launch film is directed instead by the principal's pick between animatics.
**Contents:** Ideal State · Intent Routing · Tools · Data & Config · Gotchas · Examples
## Ideal State
- Every piece was directed before it was animated: each scene carries a stated reason (a Direction beat that passed review, or the launch film's picked direction), and a plan that never passed is reported with its defects, not animated around.
- Proof passed three times, and each receipt path was handed back: on the plan before building (no brief fact dropped), on the first stills before the full render, and on the final encode, which also rendered with `render --eval <intent>` so the Assay video eval set (`video-eval`) passed on it as that intent's `## Evals` declares it. "I looked at the stills" is not evidence.
- Every render went through the seam `LIFEOS/TOOLS/HyperFrames` with every stage green; nothing ran the bare `hyperframes` CLI, and a failing stage was fixed in the composition, never bypassed.
- It reads as authored, not templated (`References/MotionDesignPhilosophy.md`): settling eases where a physical thing would ease, one focal movement per beat, text still while it is read, timing with texture, and only the transitions the content motivates. Watched once with sound off, it could not have come from a template; a piece a template could have produced got another pass.