Scene Director (Creepybits)
A Whole Cinematographer Hiding Inside a Prompt Node
- text
Type in a rough scene idea and this node wraps it in a long, very opinionated system prompt that turns whatever reads it into a "Master Scene Director." The bundled prompt is obsessed with one thing: shot composition is law. Action and framing overrule everything else, which is exactly the discipline most people need when they write video prompts and end up with flat, drifting clips. If you've ever wanted a cinematographer leaning over your shoulder while you prompt, this is the cheap version.
It's part of the "AI Creative Council" in the Creepybits suite - a set of persona nodes meant to sit between your idea and the LLM that writes your final prompt.
How it works
This node is a text combiner with a fixed preamble. At startup it reads a file called Scene_Director.md from the pack's assets/prompts/ folder - a multi-page brief describing shot types, character action directives, and thematic keyword handling. Whatever you type into the node gets appended to the end of that brief, and the whole thing comes out as one string.
It's not doing any AI work itself. It's a loader plus a concatenation. The "directing" happens because you feed this combined string to an LLM node - in this pack that's the Gemini API node - which then follows the brief and rewrites your idea into a properly composed prompt.
The input and output
- text_2 - your scene idea, action, or keywords (multiline).
- Output: text - the full brief plus your idea, ready for an LLM's system prompt input.
That's the entire surface area. One in, one out.
Installing it
It ships with ComfyUI-Creepy_nodes:
cd ComfyUI/custom_nodes
git clone https://github.com/Creepybits/ComfyUI-Creepy_nodes
restart, and it's under Creepybits/Prompt. Or use ComfyUI Manager and search "Creepy_nodes". The prompt text is bundled in the repo, so there's nothing extra to download.
Where it bites
Two things. First, that bundled brief is long - it's a full system prompt, so every time you run it you're paying tokens for it if it goes through an API. That's the point (it's doing the heavy lifting), but don't be surprised by the cost on high-volume batches. Second, the file is read once at startup. If you edit Scene_Director.md to add your own directing rules, you have to restart ComfyUI before the node picks it up. And a subtle trap: this node reads the .md file, while the pack's World Weaver Prompt node reads Scene_Director.txt - a different file. Edit one and the other won't change.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| text_2 | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| text | STRING | — |