manim-hyperframes-video
Skill4 starsChanged 36 days agoMITView on GitHub
Use when a video needs precise technical explanation visuals with Manim
In this repository29 other files it gives its agents.
- analysis-report-orchestratorSkill
- chatlab-analyzerSkill
- document-to-markdownSkill
- ecom-image-reverse-sop-shareSkill
- ecom-main-image-diagnosisSkill
- ecom-market-insight-tableSkill
- ecommerce-competitor-analyzerSkill
- ecommerce-data-analysis-workflowSkill
- ecommerce-review-analysisSkill
- ecom-one-photo-pageSkill
- ecom-page-plannerSkill
- ecom-product-assets-collectorSkill
- ecom-ranking-main-image-collectorSkill
- ecom-video-workflowSkill
- external-skill-adapterSkill
- feishu-project-weekly-reportSkill
- frontend-design-systemSkill
- full-spectrum-distillerSkill
- github-repo-dissectorSkill
- kolsprite-tiktok-opsSkill
- rpa-flow-architectSkill
- sellersprite-amazon-opsSkill
- top10stats-data-videoSkill
- video-producer-coreSkill
- webbridge-archive-publisherSkill
- web-collection-orchestratorSkill
- wechat-account-data-reviewSkill
- wechat-article-knowledge-packSkill
- wechat-group-insight-reportsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 7 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Use this as the specialized layer for technical explainer videos.
- Very specific: line 28
If none exists, use video-producer-core to create one.
- Distinctive: line 32
Use Manim for exact logic: formulas, block splitting, replicas, routing, queues, latency, graphs, architecture.
- Distinctive: line 33
Keep each Manim scene to one concept and usually 5-15 seconds.
- Distinctive: line 37
Use HyperFrames for pacing, subtitles, cards, scene transitions, title resets, sound effects, and final assembly.
- Distinctive: line 38
Treat HyperFrames as the master timeline.
- Distinctive: line 41
Use AI/B-roll for visual texture, not for precise labels or technical correctness.
- Distinctive: line 43
Avoid copyrighted clips, platform logos, and copied frames unless the user owns them.
- Very specific: line 48
Run lint, validate, inspect, ffprobe, and representative frame checks.
- Very specific: line 52
Run Manim through the environment where it is installed.
- Very specific: line 55
If HyperFrames bundled Chrome fails, set HYPERFRAMES_BROWSER_PATH to a local Chrome executable.
- Very specific: line 56
If model-based TTS fails, use Windows SAPI as a temporary Chinese narration fallback through video-producer-core.
- Very specific: line 91
Read references/workflow-template.md for a technical storyboard template, folder structure, and Manim/HyperFrames scene patterns.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Manim + HyperFrames Technical Explainer
Overview
Use this as the specialized layer for technical explainer videos. It is not a general video generator; use video-producer-core first for broad video planning, then use this skill when the video needs deterministic diagrams, formulas, system flows, or Manim + HyperFrames implementation.
Division of Labor
| Layer | Responsibility |
video-producer-core | Brief, script, storyboard, asset plan, audio plan, render verification |
| Manim | Formulas, data blocks, arrows, graphs, system mechanics, deterministic technical motion |
| HyperFrames | Master timeline, captions, title cards, callouts, AI/B-roll, transitions, audio tracks, final render |
| AI/B-roll | Atmosphere and context: data centers, chips, devices, hard drives, product shots |
Workflow
- Start from a storyboard
- If none exists, use
video-producer-coreto create one. - Mark each beat as Manim, HyperFrames, AI/B-roll, screen recording, or mixed.
- If none exists, use
- Choose Manim beats
- Use Manim for exact logic: formulas, block splitting, replicas, routing, queues, latency, graphs, architecture.
- Keep each Manim scene to one concept and usually 5-15 seconds.
- Render transparent WebM when it will sit over HyperFrames backgrounds.
- Choose HyperFrames beats
- Use HyperFrames for pacing, subtitles, cards, scene transitions, title resets, sound effects, and final assembly.
- Treat HyperFrames as the master timeline. Do not put the whole video in Manim unless it is purely mathematical.
- Generate or collect assets
- Use AI/B-roll for visual texture, not for precise labels or technical correctness.
- Record all generated prompts in the project.
- Avoid copyrighted clips, platform logos, and copied frames unless the user owns them.
- Build and verify
- Render Manim atoms first.
- Compose in HyperFrames.
- Run
lint,validate,inspect,ffprobe, and representative frame checks.
Windows Pitfalls
- Run Manim through the environment where it is installed. If Manim is in
.venv, use.venv\Scripts\manim.exe. MathTexrequires LaTeX/MiKTeX on PATH.- PowerShell scripts containing Chinese should be saved as UTF-8 with BOM for Windows PowerShell 5.1.
- If HyperFrames bundled Chrome fails, set
HYPERFRAMES_BROWSER_PATHto a local Chrome executable. - If model-based TTS fails, use Windows SAPI as a temporary Chinese narration fallback through
video-producer-core.
Commands
# Manim transparent atom
manim -ql -t --format=webm manim/scene.py SceneName -o scene_name
# HyperFrames checks
npx hyperframes lint
npx hyperframes validate
npx hyperframes inspect --samples 15
# HyperFrames draft render
$env:HYPERFRAMES_BROWSER_PATH='C:\Program Files\Google\Chrome\Application\chrome.exe'
npx hyperframes render --quality draft --output renders/draft.mp4
# Final file probe
ffprobe -v error -show_entries stream=index,codec_type,codec_name,width,height,avg_frame_rate,duration -show_entries format=duration,size -of json renders/draft.mp4Output Expectations
For a complete technical explainer job, produce:
- Script and storyboard from
video-producer-core - Manim source scenes
- Rendered Manim WebM assets
- HyperFrames composition
- AI/B-roll prompts and generated assets
- Audio sources and final MP4
- Verification notes and known limitations
References
Read references/workflow-template.md for a technical storyboard template, folder structure, and Manim/HyperFrames scene patterns.
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.

