VRGDG_PromptCreatorUI

Step one of VRGameDevGirl's music video workflow, per the README, is "customize the Prompt Creator to define style, mood, and scenes." VRGDG_PromptCreatorUI is that control surface - and like the pack's other UI nodes, it has zero inputs and zero outputs. All its value is in the widgets it shows you.

If that sounds anticlimactic, remember what the workflow is doing: it's transcribing your song into a per-scene prompt map and handing that map to an LLM node to flesh out scene prompts. Someone has to hold the creative direction - the style, mood, subject, scene list - that everything downstream is built from. This node is where you type it. It's the front end of the whole pipeline.

Why it has no ports

The node isn't transforming data at runtime; it's a settings panel whose state lives in the workflow JSON alongside everything else. The nodes that actually read your creative direction (the prompt builders and the Qwen LLM node in the pack) pull from that shared state. So you don't wire this into anything - you fill it in, and the graph already knows.

That's the same design as VRGDG_Part3WorkflowUI: these UI nodes exist to keep a whole section's controls in one labeled place instead of scattering them. It's organizational more than functional, and that's fine.

What to actually do

Treat it as a brief. Before you feed audio into the pipeline, write the creative direction here: the main character or subject, the mood, the visual style, any scenes you already know you want. Get specific - the workflow's whole point is that it turns your reference image plus this direction into consistent scene prompts, and the quality ceiling of the final video is set right here.

Two practical notes. First, this is the original Prompt Creator UI; the pack also ships a VRGDG_PromptCreatorUI_V2. If a workflow loads the V2, use the V2 - the two aren't interchangeable ports-wise, and the newer one is what the current workflows expect. Second, because it's a UI-only node, bypassing it changes nothing. The creative direction still lives in the workflow state.

Installing it

It ships in the pack, so install once:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl

Restart ComfyUI, or use ComfyUI Manager → search vrgamedev. No model files for this node itself, though the workflow it anchors expects the pack's kornia, librosa, and imageio dependencies installed.

The honest take

A node with no data ports feels like a gimmick until you run a workflow where it's genuinely the highest-leverage text field in the graph. Here it is. Fill it in carefully and the rest of the pipeline behaves; phone it in and you'll spend hours patching scene prompts downstream that this one screen could have fixed.