---
name: media-director
description: Use when a user asks to create, turn into, redesign, animate, or repurpose a real UI, product demo, architecture, creative idea or evidence into high-quality videos, HTML/SVG motion graphics, screenshots, LinkedIn carousels or multi-platform media; also when planning the associated DAM/CMS workflow.
---

# Media Director — evidence-first creative production

Read `references/quality-contract.md` and `references/asset-contract.md` before producing output. Use the existing CIS Video Production OS as technical canon when GitHub access is available; preserve its current adapter choices and revision status rather than inventing new defaults.

## Do the work, not a generic plan

1. Resolve **one business job** and intended audience, primary takeaway, original insight, strongest proof, conversion action and brand. Use known user context; do not ask again unless a missing item prevents production. If output is requested, create the best artifact that the observed host tools can produce now.
2. Classify source: real product/commit/deployment; supplied screenshot; verified public reference; founder recording; authored fiction. Keep these lanes distinct; conceptual UI must never be presented as product evidence.
3. Record evidence inventory: source URLs, exact revision/hash, claim, approved identity/rights, unknowns, unavailable proof. Quote only short verified portions. Block publication claims missing proof.
4. Propose **three structurally different** creative directions internally; select one and explain the decisive mechanism. Use story relation (tension, change, comparison, journey, reveal), not a pile of feature cards.
5. Define narrative contract: hook, reader/viewer question for every beat, beat-to-visual map, proof dependency, payoff, CTA. Explain what meaning each interaction or motion reveals.
6. Specify ONE canonical editable scene or source composition. Prefer HTML/CSS/SVG/React for interactive illustrations; verified browser capture for existing product behavior; HyperFrames for new deterministic motion; Remotion for existing React-specific workflows; Higgsfield for invented cinematic imagery; Descript for founder A-roll. Use only tools actually available; do not claim rendered exports from an inline UI.
7. Produce appropriate derivatives: interaction, SVG, still, 4:5 carousel, 9:16 short, 16:9 demo, captions and source docs. Not every campaign needs all derivatives. Each derivative must preserve source facts while using its own editorial construction.
8. Critique the still BEFORE motion. Evaluate contrast, layout, mobile legibility, crop, density, color semantics, brand recognition, typographic craft and useful originality. For motion, inspect representative start/mid/end/loop frames and verify audio with actual playback when possible.
9. Generate a manifest per `references/asset-contract.md`, original source locations, revision/provenance, QA verdict and release status; never claim persisted storage, exported video, upload, scheduled post or human approval without a tool receipt.
10. Return actual artifact links and changed files when they exist; otherwise deliver a production-ready scene specification or working source, clearly marked not rendered. End with one owner, one blocked gate and the next action only where relevant.

## Model/agent and cost policy

Use task-selected available models, not invented Astra/Sol/Terra sessions. Parallelize independent research, concept and renderer jobs only when actual subagent tooling is observed. Assign a budget before paid generation; no implicit paid retries. Prefer deterministic adjustments to regenerate only affected frames. Do not put source video bytes or private account credentials in model context.

## Completion

Every release candidate needs `claim_provenance`, `creative_direction`, `source_revision`, `asset_manifest`, `quality_report`, `publication_authority` and `status_receipts`. See the examples in `references/asset-contract.md`. Missing evidence is `HOLD`, not success.

## Executable reference

The bundled `scripts/render_media_pack.py` and `assets/reference/scene.json` provide a
**conceptual** offline, source-driven example. With supported local libraries and
ffmpeg available, render SVG, PNG, vector PDF, mobile HTML, 9:16 silent MP4,
captions and a manifest. Run `scripts/verify_media_manifest.py` as a separate
byte-integrity check. Render artifacts do not prove visual QA, human approval,
product behavior, DAM upload or publication. Use actual connected product capture
for real product claims.