JB · Outfit Block

In the JB pipeline, an outfit used to be three nodes: Outfit Generator produces garments with color tags, Color Generator makes the palette, and a combiner merges them and substitutes the colors. JB · Outfit Block collapses all of that into a single node. Pick an outfit set, twist the sliders, and out the other side comes a fully resolved JSON outfit - colors already baked in as real color names, structured so it drops straight into a JB · Stitcher under your character's title.

It's the "one-shot combo" pattern the JB suite is built around, and it exists to kill the most annoying part of structured prompting: assembling a coherent outfit and keeping the colors consistent across every garment. With the block, "coherent" is a property of the pipeline, not a thing you hope for.

What you get

There are 446 outfit sets in the dropdown - business, casual, aerobic, athleisure, beach, and on down, many split female//male/ and by activity. The node reuses the exact same outfit_lists/ text-file data as the standalone FVM_OutfitGenerator, and the Edit List modal edits those source files directly from the node - same instant-apply behavior, no restart. You get the same garment toggles (enable_top, enable_bottom, enable_footwear, enable_headwear, enable_outerwear, enable_accessories, enable_bag), the formality and coverage sliders, print_probability and text_mode for prints/typography, and the overrides string for hand-fixing a single slot (bottom: exclude skips it entirely).

The color section is Color Generator folded in: num_colors (2–8), harmony_type, palette_style, vibrancy, contrast, warmth. Where the standalone outfit node emits #primary#-style tags waiting for a separate replace step, this block resolves them itself - the JSON comes out with actual color names already in place.

The outputs

• outfit_json - the structured outfit, colors resolved. Feed this to a Stitcher's input_N.
• outfit_string - the same content as a flat string, for encoders that prefer a sentence.
• palette_summary - a human-readable rundown of the palette and what each role color was.

Because colors are baked in, the outfit block is deterministic per seed the way the generator is - same seed, same set, same sliders, same outfit and palette every run.

Installing

cd ComfyUI/custom_nodes
git clone https://github.com/ping1979ping/comfyui-FVMtools

Zero extra dependencies. Restart ComfyUI; it lives under FVM Tools/JB.

When to use it vs. the standalone nodes

Use the block when you're building a JB character document and want one node per character slice - outfit, face, location - each producing JSON. Use the standalone FVM_OutfitGenerator when you want the tagged prompt flow (with Prompt Color Replace downstream) or when you need to mix a fixed palette across multiple characters, so every character shares the same wardrobe colors. The block gives each character its own palette; the standalone flow gives them all one. That's the whole decision, and it's worth making deliberately.