Prompt Builder B (CCN)

Prompt Builder B is the sibling of Prompt Builder with a different set of section labels aimed at a different way of thinking about a prompt. Where the plain version splits things into scene/features/details (a storytelling split), this one uses quality, style, mood, motion, and general - a production-ish split that maps nicely onto how people actually describe a shot: technical quality first, then artistic direction, then emotion, then movement.

That's the entire difference. Same mechanism, same statelessness, same output.

What you get

Five multiline text boxes, empty ones skipped, joined by a delimiter (default \n\n), with an optional prefix_sections toggle that prepends each label (mood: brooding and tense). One prompt STRING comes out, ready for a CLIP Text Encode.

The practical split of the labels:

• quality - "masterpiece, highly detailed" style descriptors, if your model speaks them (on LLM-encoded models these can be inert, so treat as a slot, not a guarantee).
• style - artistic direction: painterly, photoreal, specific aesthetics.
• mood - emotional tone, the thing that's underused in most prompts.
• motion - movement and dynamics, which matters a lot for video models.
• general - the catch-all for anything that doesn't fit the above.

Because it's just string assembly, you can wire the output anywhere a STRING is accepted - not just into a text encoder but into a filename pattern, a caption, or a Prompt Store chain. Nothing here remembers anything between runs; if you want these exact labels with session persistence, that's Prompt Store B, which uses the same quality/style/mood/motion/general vocabulary.

Install

Same pack, one install:

cd ComfyUI/custom_nodes
git clone https://github.com/valkymaera/ComfyCollectorNodes

then restart ComfyUI, or install via ComfyUI Manager by searching "ComfyCollectorNodes". No model downloads, no extra dependencies.

Where people get burned

The same delimiter trap as its sibling - the field holds the literal \n\n, so don't hand-edit it unless you know you want a different glue. And again: it doesn't store anything. Blank a section and it just disappears from the assembled prompt. If your workflow is already running both this node and the store version with the same store name, note that they share the vocabulary but the builder never writes to storage - so they won't collide the way two stores might.