motion-graphics: point the Builder at hyperframes-creative's motion-principles.md
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start with skills/motion-graphics/agents/builder.md and skills/motion-graphics/SKILL.md to trace the Builder's dispatch context, then inspect categories/charts/module.md and categories/stat/module.md. Verify that the motion-principles.md and data-in-motion.md references are added at the requested points and that all links resolve to the existing hyperframes-creative files.
Written by the indexing model from the issue text.
Description
Problem
skills/motion-graphics never references skills/hyperframes-creative (no mention in any file on main). As a result, hyperframes-creative/references/motion-principles.md is not on the motion-graphics read path, even though motion-graphics is the most motion-first workflow in the repo.
I checked whether its guardrails are covered elsewhere on that path (SKILL.md, agents/director.md, agents/builder.md, references/builder-contract.md, references/motion-vocabulary.md, plus the SKILL.md of hyperframes, hyperframes-core and hyperframes-animation). They mostly are not:
| motion-principles.md guardrail | Covered on the motion-graphics path? |
|---|---|
| Vary eases (≤2 tweens per scene with the same ease) | No |
.out for entrances, .in for exits, .inOut for moves |
No (only per-primitive examples in motion-vocabulary.md) |
| Vary duration (slowest scene ~3× the fastest) | No |
Vary entrance direction (not always y:30, opacity:0) |
No |
| Build / breathe / resolve scene structure | Partly (categories/kinetic-type only: Hook → Build → Punch → Resolve) |
| Stagger by importance, total stagger < 500ms | No |
| Exits faster than entrances | No |
| Offset the first tween 0.1–0.3s | No |
The only route to the file today is indirect (hyperframes-animation/adapters/animate-text.md, or the capability table in hyperframes/SKILL.md), so whether the Builder reads it depends on the agent's own initiative.
hyperframes-creative/references/data-in-motion.md has the same gap for the charts and stat categories.
Proposed solution
A small docs-only change:
skills/motion-graphics/agents/builder.md— add a line under "Critical correctness" (or a new "Motion quality" heading): read../hyperframes-creative/references/motion-principles.mdbefore writing the timeline.skills/motion-graphics/SKILL.mdStep 4 — add that file to the Builder's dispatch context list.skills/motion-graphics/categories/charts/module.mdandcategories/stat/module.md— reference../hyperframes-creative/references/data-in-motion.md.
Alternatives considered
Inlining a condensed version into references/motion-vocabulary.md. This avoids a cross-skill read but duplicates content that would drift from the original, so a link seems better.
Alternatives considered
Inlining a condensed version into references/motion-vocabulary.md. This avoids a cross-skill read but duplicates content that would drift from the original, so a link seems better.
Additional context
While building short HTML motion pieces with an AI coding assistant (outside HyperFrames), I hit exactly the failure modes this file warns about: uniform easing, missing exits, flat timing. That is what led me to compare the motion-graphics read path against motion-principles.md. I have not measured the effect inside the motion-graphics workflow itself.
- Dominant language
- TypeScript
- Stars
- 54.1k
- Forks
- 4.9k
- Avg merge
- 7h 29m
- Merged PRs (30d)
- 778
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from heygen-com/hyperframes
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
heygen-com/hyperframes#5027 ·
Maintainers usually reply within 1 day
-
fix(producer): propagate useGpu to HDR layered streaming encoderPossibly taken @Monster-GM claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
heygen-com/hyperframes#5002 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
heygen-com/hyperframes#4702 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Studio catalog prompt editor has no accessible namePossibly taken @lorenzozanee claimed this 12 days ago. Openbug difficulty/easy triage/ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
heygen-com/hyperframes#4384 ·
Maintainers usually reply within 1 day
-
lint: validate composition variables declared on supported root elementsMay be free again A pull request for this issue was closed without being merged. Openbug difficulty/easy triage/ready
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
heygen-com/hyperframes#4383 ·
Maintainers usually reply within 1 day
All issues in heygen-com/hyperframes
Similar issues
-
fix(data-lake): wizard source step still previews the local slug, not the server-disambiguated oneOpendata-lake
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
bug ios mobile priority:P1
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
streamplace/streamplace#1351 ·
Maintainers usually reply within 2 days