game-trailer-production

What it does

Guides an agent to produce game trailers and promos that reflect the real game, balancing creativity with truth, platform constraints, and legal reviews. It emphasizes treating trailers as both creative work and regulated marketing, requiring truthfulness in gameplay representation and adherence to review processes.

How it works

• First, classify the intended primary deliverable (e.g., Announcement teaser, Gameplay trailer, Launch trailer, DLC/update trailer, Store-page video, Social cutdown, or Generated/engine-capture hybrid promo) and decide structure accordingly.
• Compile an intake production brief with sections such as Game identity, Build facts, Game truth, Trailer goal, Audience, Asset inputs, Constraints, and Reviewers.
• Apply Truthfulness rules to maintain a truth ledger, including proof requirements for Gameplay shot, Feature claim, Performance claim, Multiplayer/online claim, Content claim, Review/award quote, and Generated shot.
• Use specific labeling for shot types (e.g., "Gameplay captured in-engine", "Pre-alpha / alpha / beta footage", "Cinematic trailer", etc.).
• Follow Capture planning steps: select capture pillars, map to shot structure, assign capture type, define technical settings, and create a shot log.
• Follow detailed UI/HUD treatment guidelines to decide what to show or hide for each trailer type.
• Use beat maps to structure each beat around a viewer question, with fields like Beat ID, Time range, Purpose, Shot IDs, Audio moment, On-screen copy, etc.
• Plan audio with Music, SFX, VO, and title cards, ensuring rights, localization, and clear attribution; use evergreen on-screen copy where possible and provide accurate captions.
• Apply Generated b-roll boundaries to ensure any generated content is clearly distinct from actual gameplay proofs, with provenance and rights considerations.
• Maintain Claims, ratings, and legal escalation procedures, verifying claims with evidence and escalating for approval if rating-sensitive material, licensed assets, or rights issues arise.
• Enforce Accessibility and safety QA on captions, readability, and flash risk throughout production.

When to use it

Use when planning, scripting, capturing, generating, editing, localizing, reviewing, or QAing game marketing videos where gameplay truthfulness, platform/store constraints, ratings, accessibility, claims, CTA metadata, and rights provenance matter.

What it can touch

The skill references tools (claude-code, codex, copilot, cursor) for crafting scripts, planning, and QA tasks as part of the production workflow. It requires input data about game identity, build facts, and trailer goals, and outputs a structured plan and truth ledger.

Caveats

• Requires careful handling of claims and rights; escalation is advised for rating-sensitive material, licensed content, or third-party IP.
• Do not misrepresent gameplay or features; truth ledger must be maintained with documented proof for all claims.
• Accessibility requirements should be integrated early, not retrofitted later; ensure captions and readability meet guidelines.