agentleFS
coltonjosephdean-rgbcoltonjosephdean-rgb/Hyperframes-colton.ai.dean/AGENTS.md

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
  1. Very specific:

    After creating or editing any .html composition, run the linter before considering the task complete:

    line 46
  2. Very specific:

    Every timed element needs data-start, data-duration, and data-track-index

    line 56
  3. Very specific:

    Only deterministic logic — no Date.now(), no Math.random(), no network fetches

    line 65

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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/hyperframes

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.

SkillCommandPurpose
hyperframes/hyperframesAuthoring compositions, captions, TTS, audio-reactive animation
hyperframes-cli/hyperframes-cliCLI commands (init, lint, preview, render, transcribe, tts, doctor)
gsap/gsapGSAP animation reference
hyperframes-registry/hyperframes-registryInstalling catalog blocks/components
website-to-hyperframes/website-to-hyperframesURL → video (7-step capture-to-video pipeline)
make-a-video/make-a-videoBeginner-friendly end-to-end video creator
short-form-video/short-form-video9:16 vertical talking-head + motion-graphic playbook
study-creator/study-creator <url>Study a reference creator's video; rolls up a style fingerprint
feedback/feedbackCapture what worked/didn't on a finished video; updates PREFERENCES.md
setup/setupFirst-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 terminal

Project Structure

  • index.html — main composition (root timeline)
  • compositions/ — sub-compositions referenced via data-composition-src
  • assets/ — 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 lint

Fix all errors before presenting the result.

Key Rules

  1. Every timed element needs data-start, data-duration, and data-track-index
  2. Visible timed elements must have class="clip" — the framework uses this for visibility control
  3. GSAP timelines must be paused and registered on window.__timelines:
    window.__timelines = window.__timelines || {};
    window.__timelines["composition-id"] = gsap.timeline({ paused: true });
  4. Videos use muted with a separate <audio> element for the audio track
  5. Sub-compositions use data-composition-src="compositions/file.html"
  6. Only deterministic logic — no Date.now(), no Math.random(), no network fetches

Documentation

Full docs: https://hyperframes.heygen.com/introduction

Machine-readable index for AI tools: https://hyperframes.heygen.com/llms.txt

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.