video-creationlisted

# Video creation This skill executes Design's bounded production contract. It does not invent strategy, copy, templates, or a second workflow. Read the campaign Artifact, `.agents/company/departments/design/README.md`, `templates/registry.json`, `templates/video/narration.json`, `presets.json`, `system/production.css`, and the shared `brand-motion.css` before rendering. ## Inputs and selection Require a strategy-complete campaign with `campaign_id`, `batch_id`, `item_id`, `content_id`, one idea, complete `narration.script`, ordered scenes, design identity, CTA, and the correct platform preset. Select one registered archetype per item/platform. No batch repeats one template when the registry can cover the batch; larger batches use balanced round-robin counts, no adjacent repeat, and balanced control/variant cells. Never silently fall back or rename legacy templates. The script is written as one story before scene splitting: `Hook → Pain/Context → Why it matters → AI/workflow mechanism → SpielOS role → Outcome → CTA` Keep the registry scene order and one delivery intent per scene. The hook is a plain frame thumbnail; no glass-card or still-title overlay. ## Creative and voice contract Use the flat Gruvbox-dark motion language: centered Outfit 800, semantic tokens, restrained Boxicons, official logo, centered `spielos.xyz` footer, and one quiet journey line with solid completed route, dashed route ahead, and bullseye goal. No 3D, mockups, glassmorphism, decorative card s