mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-15 13:58:20 +00:00
Five-way review of the section against docs.json, catalog pages, and skills. Fixes: stale /hyperframes-media skill row (real name /media-use) plus missing music-to-video and slideshow workflow rows; caption identity misattributions (keynote/documentary are scene-embedded, stomp carries no rail); prompts violating the guide's own ambient-idle rule; grounded keying rationale (u2net_human_seg); broken forward references; nested-backtick code spans; brand casing and frontmatter dash consistency throughout. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
18 lines
1.5 KiB
Plaintext
18 lines
1.5 KiB
Plaintext
---
|
|
title: The specification dial
|
|
description: "Spec density controls how far the result drifts from what you imagined — not whether it works."
|
|
---
|
|
|
|
How much you specify sets how much you delegate — it controls how far the result can drift from what you imagined, not whether it works. Mood-level prompts ("snappy", "cinematic") get a designer's interpretation: coherent, but the agent picks the colors, staging, and details. Dense specs — hexes, timestamps, easings, pinned techniques — get *your* frame.
|
|
|
|
Three settings:
|
|
|
|
1. **Mood words** — "a warm, minimal logo sting". Fastest to write; the agent owns the look.
|
|
2. **Style tokens** — exact hexes, named textures ("halftone-dot", "paper-cut matte", "8-bit pixel"), type direction ("condensed caps", "thin geometric sans, wide tracking"). Cheap precision, no downside.
|
|
3. **Full visual spec** — every element gets shape + color + position + timing (see [visual specs](/prompting/visual-specs)). Use when you're recreating a specific look.
|
|
|
|
Density never hurts — a stronger model just uses less of its own taste. It matters most for technique choices a smaller model won't default well. Two worth pinning every time:
|
|
|
|
- **3D**: any real depth, lighting, or camera motion → say **"Three.js via the adapter"**. CSS perspective transforms read flat on lighting-critical scenes, and Three.js is a supported seek-safe runtime.
|
|
- **Sequencing**: resolve simultaneity in the text. "The counter fades out and READY stamps in at 4s" produces an overlap; "fades out fully by 4.2s; at 4.2s READY stamps in" doesn't.
|