Hyperframes-colton.ai.dean
AGENTS.md19 starsChanged 5 months agoMITView on GitHub
This workspace uses AI agent skills for framework-specific patterns. Install them if not already present: Skills encode patterns like window.__timelines registration, data-* attribute semantics, and shader-compatible CSS rules that are not in generic web docs. Using them produces correct compositions from the start. After creating or editing any .html composition, run the linter before considering the task complete: Fix all errors before presenting the result. Full docs: https://hyperframes.heygen.com/introduction Machine-readable index for AI tools: https://hyperframes.heygen.com/llms.txt
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 46
After creating or editing any .html composition, run the linter before considering the task complete:
- Very specific: line 56
Every timed element needs data-start, data-duration, and data-track-index
- Very specific: line 65
Only deterministic logic — no Date.now(), no Math.random(), no network fetches
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HyperFrames Composition Project
Skills
This workspace uses AI agent skills for framework-specific patterns. Install them if not already present:
npx skills add heygen-com/hyperframesSkills encode patterns like window.__timelines registration, data-* attribute semantics, and shader-compatible CSS rules that are not in generic web docs. Using them produces correct compositions from the start.
| Skill | Command | Purpose |
hyperframes | /hyperframes | Authoring compositions, captions, TTS, audio-reactive animation |
hyperframes-cli | /hyperframes-cli | CLI commands (init, lint, preview, render, transcribe, tts, doctor) |
gsap | /gsap | GSAP animation reference |
hyperframes-registry | /hyperframes-registry | Installing catalog blocks/components |
website-to-hyperframes | /website-to-hyperframes | URL → video (7-step capture-to-video pipeline) |
make-a-video | /make-a-video | Beginner-friendly end-to-end video creator |
short-form-video | /short-form-video | 9:16 vertical talking-head + motion-graphic playbook |
study-creator | /study-creator <url> | Study a reference creator's video; rolls up a style fingerprint |
feedback | /feedback | Capture what worked/didn't on a finished video; updates PREFERENCES.md |
setup | /setup | First-run onboarding — creator profile, reference reels, brand colors |
Commands
npx hyperframes preview # preview in browser (studio editor)
npx hyperframes render # render to MP4
npx hyperframes lint # validate compositions (errors + warnings)
npx hyperframes lint --json # machine-readable output for CI
npx hyperframes docs <topic> # reference docs in terminalProject Structure
index.html— main composition (root timeline)compositions/— sub-compositions referenced viadata-composition-srcassets/— media files (video, audio, images)meta.json— project metadata (id, name)transcript.json— whisper word-level transcript (if generated)
Linting — Always Run After Changes
After creating or editing any .html composition, run the linter before considering the task complete:
npx hyperframes lintFix all errors before presenting the result.
Key Rules
- Every timed element needs
data-start,data-duration, anddata-track-index - Visible timed elements must have
class="clip"— the framework uses this for visibility control - GSAP timelines must be paused and registered on
window.__timelines:window.__timelines = window.__timelines || {}; window.__timelines["composition-id"] = gsap.timeline({ paused: true }); - Videos use
mutedwith a separate<audio>element for the audio track - Sub-compositions use
data-composition-src="compositions/file.html" - Only deterministic logic — no
Date.now(), noMath.random(), no network fetches
Documentation
Full docs: https://hyperframes.heygen.com/introduction
Machine-readable index for AI tools: https://hyperframes.heygen.com/llms.txt
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- feedbackSkill
- gsapSkill
- hyperframes-cliSkill
- hyperframes-registrySkill
- hyperframesSkill
- make-a-videoSkill
- setupSkill
- short-form-videoSkill
- study-creatorSkill
- website-to-hyperframesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

