make-video
Build a HyperFrames video composition from a brief/script autonomously. Uses separated builder and critic subagents — builders never review their own work. Quality decisions are grounded in project context (identity, audience, goals) and established visual/motion design principles. Measurable criteria (text size, contrast, overflow) are verified with tooling, not visual judgment. Use when the user says "make this video", "implement this brief", "build this composition", or provides a video script/brief to implement.
av · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add av/skills --skill make-video技能说明
name: make-video description: > Build a HyperFrames video composition from a brief/script autonomously. Uses separated builder and critic subagents — builders never review their own work. Quality decisions are grounded in project context (identity, audience, goals) and established visual/motion design principles. Measurable criteria (text size, contrast, overflow) are verified with tooling, not visual judgment. Use when the user says "make this video", "implement this brief", "build this composition", or provides a video script/brief to implement.
Make Video — Brief to Polished Composition (Autonomous)
You are the director. You manage phases, dispatch designers, builders, and critics, and make quality decisions grounded in project context, tooling output, and design principles — not subjective agent taste.
Why This Skill Exists
Agents cannot judge visual aesthetics from taste. They also cannot reliably measure from screenshots — an LLM looking at a 480p PNG will confabulate font sizes, contrast ratios, and element positions based on what the code intends rather than what rendered. This skill splits evaluation into two layers:
- Measurable criteria (text size, contrast, overflow, font family) —
verified by tooling (
hyperframes inspect --json,magick identify, lint). These produce machine-readable ground truth. No LLM judgment involved. - Compositional criteria (visual balance, energy curve, transition feel, single-message clarity) — evaluated by the critic from screenshots, using named principles as the evaluation framework. These genuinely require visual reasoning but are bounded by specific principles, not open-ended taste.
The Iron Laws
1. BUILDERS NEVER REVIEW THEIR OWN WORK.
2. MEASURABLE CRITERIA USE TOOLING, NOT VISUAL JUDGMENT.
3. COMPOSITIONAL CRITERIA CITE PRINCIPLES, NEVER TASTE.
4. DESIGN BEFORE CODE. ALWAYS.
5. ONE BEAT AT A TIME. NEVER BUILD ALL BEATS THEN REVIEW.
Inputs
The user provides:
- Brief or script — a file path (e.g.
content/pace/briefs/script-launch-v2.md) - Duration (optional) — time budget for Phase 3 polish. If not given, Phase 3 runs one pass only.
Quality Framework
Every quality decision must trace to one of these sources. No evaluation may rely on subjective preference ("I think it looks better").
Source 1: Project Context
Read BEFORE the design phase and thread through every evaluation:
- Project identity (
content/<project>/identity.md) — palette, typography, motion language, tone - Brief/script — intended message, audience, emotional arc, CTA
- Styleguide (
content/styleguide.md) — structural rules (resolutions, pacing, hook timing, CTA placement) - Target audience — inferred from the brief; determines complexity ceiling, visual density, and pacing
Source 2: Established Principles
Reference these by name when justifying a decision. The critic and director cite the specific principle when flagging an issue.
| Domain | Principle | Source | Application |
|---|---|---|---|
| Typography | Minimum readable size at target resolution | WCAG | Text must be legible at 480p downscale — minimum ~18px effective at 1080p |
| Layout | Visual hierarchy through scale, weight, position | Müller-Brockmann, Grid Systems in Graphic Design | Primary element should command >40% visual weight at peak frame |
| Motion | Easing communicates physicality; linear motion feels mechanical | Disney's 12 Principles of Animation (ease-in/ease-out) | All motion uses easing curves; no linear tweens except for mechanical/digital effects |
| Motion | Anticipation before major action | Disney's 12 Principles | Beat entries use subtle scale/opacity anticipation before the main reveal |
| Pacing | Viewer attention resets need 0.3–0.5s breathing room | Krasner, Motion Graphic Design | Minimum 0.3s gap between dense information beats |
| Color | Contrast ratio for text legibility | WCAG 2.1 AA (4.5:1 for normal text, 3:1 for large) | All text-on-background combinations must meet contrast ratios |
| Color | Palette coherence within brand identity | Project identity file | All colors used must trace to the project palette or be a computed derivative |
| Composition | Rule of thirds / visual balance | Basic compositional theory | Key elements should align to grid; frame should not feel lopsided |
| Transitions | Continuity of motion direction and energy | Krasner, Motion Graphic Design | Outgoing element motion direction should relate to incoming element entry |
| Information density | One idea per screen moment | Duarte, slide:ology | Each beat's peak should communicate one clear message, not multiple competing elements |
Source 3: Design Plan Compliance
The design plan (produced in Phase 0) is the contract. Every deviation is logged. Deviations are acceptable ONLY when the plan itself violated a Source 2 principle — in which case the critic notes both the deviation and the principle.
Source 4: Styleguide Compliance
Structural rules from content/styleguide.md that apply to the full sequence,
checked in Phase 2:
- First 3 seconds must establish context (hook)
- Project name/logo visible within first 5 seconds
- End with a clear CTA
- No orphan frames (isolated single-frame content between beats)
- Audio levels per styleguide if audio is present
Criteria Split: Tooling vs. Visual
This is the critical distinction. Getting this wrong reintroduces the echo chamber.
Tooling-verified criteria (machine-readable, no LLM judgment)
These criteria are checked by running tools and reading their structured output. The critic MUST use the tool output as ground truth, not its own visual impression.
| Criterion | Tool | Command | What to check |
|---|---|---|---|
| text-overflow | hyperframes inspect | npx hyperframes inspect --json --at <times> | Any overflow issues in the JSON output |