Clothing 2

Clothing 2 is the pack's "summer" wardrobe slot - README's mapping, not mine - and like its siblings it starts empty. Dropdown shows just custom_input until you add files. So before you can use it you need to buy in on the whole idea of the Prompt String Selector pack: prompts as text files on disk, swapped by dropdown, kept out of the way of the actual workflow.

If you're building one of those "same character, many outfits" gallery runs - which is a huge chunk of what people actually do with character LoRAs - this is the node that lets you treat the outfit as a parameter instead of an edit. And splitting by season means your summer list doesn't bury your winter list. The trade is upfront: you type each outfit description once, into a file, instead of into the prompt box every run.

How it works

The node reads ComfyUI/custom_nodes/ComfyUI-Prompt-String-Selector/data/clothing2/, created automatically on first run. Every .txt file in it becomes a dropdown option. File naming is the whole game: 01_tank_top.txt, 02_swimwear.txt, and the leading number is what comes out as id. Comments (//, /* */) inside files are stripped before output.

Inputs and outputs

• clothing2 - dropdown of your summer outfits.
• clothing2_custom - multiline override; custom_input uses this box's text, id is 0.

Outputs: text (STRING, comma-terminated for chaining) and id (INT). The id is the clever bit - it lets a Prompt Switch node or your own logic pick an outfit numerically, so you can randomize or sequence outfits across a batch without touching the graph.

Install

Via ComfyUI Manager (search "Prompt String Selector") or:

cd ComfyUI/custom_nodes
git clone https://github.com/itom0717/ComfyUI-Prompt-String-Selector.git

Restart ComfyUI. No dependencies, no models - the whole pack is the Python standard library. Nothing to go wrong at install time.

Gotchas

Same as every selector here: new files appear only after a restart, and since you're populating from zero, batch your files. One more thing worth saying about outfit blocks specifically - keep them prompt-shaped, not paragraph-shaped. A tag-based checkpoint wants sundress, floral pattern, bare shoulders-style comma lists. Write the file the way you'd write the prompt, because that's literally what it is.