Cinematic Horror Episode Film · skill Open Skill công khai

Cinematic Horror Episode Film

A cinematic horror workflow that turns story ideas into complete episodic videos with consistent characters, atmospheric visuals, suspenseful cinematography, lighting, sound, and storytelling.

@smartaitools22

Film

8 1 11

https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/4029457/2026-09-07/ens5xrbn.png

# Cinematic Horror Episode Film

## When to use
- The user wants a ~30-second, 16:9 landscape cinematic horror episode from a one-liner, episode brief, script, or reference image(s).
- The user wants the **next episode** (sequel) of a horror series, preserving exact character appearances, locations, injuries/props, and the established emotional color system.
- The user wants a **single-stage revision** of an episode already made with this skill (rewrite the script, restyle the color system, change one shot, regenerate narration/music, remix), keeping everything else untouched.

## Core principles (locked for every episode)
- Preserve exact character appearance and continuity: face, hair, clothing, body proportions, distinctive features — across all frames, shots, and episodes.
- Maintain environmental continuity through the whole episode: locations, injuries, supernatural effects, props, and time-of-day/weather changes.
- Establish the episode's emotional color system up front and apply it consistently in every frame, shot, and grade description.
- Prioritize visual storytelling; use narration/dialogue only when necessary and keep it restrained.
- Build tension gradually through composition, shadows, camera movement, lighting changes, silence, and atmosphere.
- Use cinematic horror cinematography: realistic environments, dramatic lighting, controlled camera movement, detailed visual effects, suspenseful pacing.

## Built-in memory (cross-session continuity)
- At the start of every task, call `memory_query` for key `horror_episode_film:series_registry` (and `horror_episode_film:user_prefs` if it exists). If absent, this is a new series — create and confirm a series key with the user (name it from their brief or ask).
- Keep a compact **series registry** in memory under `horror_episode_film:series_registry`: series_key, episode list, per-episode character reference asset ids, location reference asset ids, the emotional color system (verbatim wording), continuity notes (injuries, props, world state), narration voice style, and hooks for the next episode.
- After finishing an episode — or after any stage that changes continuity (new character variant, new injury, new location) — call `memory_store` to update the registry under the same keys. Store asset ids and one-line notes, never full scripts.
- When the user starts a later conversation and asks for episode N+1 or an edit, first query memory to restore the registry, then only work from the stored refs/color system; do not re-derive appearances from scratch.

## Steps

### 1. Understand the request
- If the user supplied a reference image (character, location, style frame), call `recognize_image` first to capture exact appearance details, then reuse that image as a reference asset in later steps.
- Determine: is this a new series or a sequel? For a sequel, query memory (above) and adopt the stored refs and color system. For a new series, establish a new registry entry.
- Nail down the episode working title and a one-line logline; if the brief is ambiguous, ask one short clarifying question before generating.

### 2. Develop the episode structure
- Write a compact episode bible: a 3-beat structure — (1) cold dread setup, (2) escalation with a reveal, (3) payoff/scare plus an after-hook — expanded into **6–8 shots of ~4–5 seconds each (total ≈30 s)**.
- For each shot record: content, camera movement (slow push-in, dolly, handheld drift, whip pan, static with subtle zoom), lighting change, sound cue, and how it expresses the emotional color system.
- Save the bible with `create_document` (name `Horror Episode Film — <Working Title>`, entity_type='documents') so the user can read and revise it.
- If the user asked for a single-stage revision only, skip the unchanged stages and touch exactly the requested stage (minimal diff on existing assets/refs).

### 3. Establish the emotional color system
- Define this episode's system explicitly (example: "cold teal shadows, desaturated amber