Clothing 1

Here's the honest review: the Clothing 1 selector ships with no prompt files at all. Open its dropdown and the only option is custom_input. That's not a bug - it's the intended workflow. The author structured the pack's four clothing selectors as a wardrobe: Clothing 1 for spring, Clothing 2 for summer, Clothing 3 for autumn, Clothing 4 for winter. You're expected to fill in the outfits.

So the first thing to know: this is a "bring your own data" node. If that puts you off, fair - but the payoff is that once you've populated it, changing a character's outfit is a dropdown click, and you can do it per season without mixing wardrobes into one giant list. For anyone batch-generating the same character across scenes, that's genuinely useful.

How it works

Reads ComfyUI/custom_nodes/ComfyUI-Prompt-String-Selector/data/clothing1/ - a folder that doesn't even exist until you run ComfyUI once (the node creates it). Drop 01_spring_dress.txt, 02_blazer.txt, whatever, restart, and they become dropdown entries. Same rules as every selector in the pack: filename minus extension is the label, the leading number is the id output, and // or /* ... */ inside a file gets stripped.

Inputs and outputs

• clothing1 - the dropdown. Just custom_input until you add files.
• clothing1_custom - multiline override. Pick custom_input and this box's contents are used instead; id becomes 0.

Outputs: text (STRING, comma-terminated so it chains into an Aggregator) and id (INT). Wire text into your positive prompt path.

Install

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

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

Restart. There's no requirements.txt, no pip install step, no model downloads - pure Python standard library, so the install itself is as safe as custom nodes get.

Gotchas

The restart-to-refresh dropdown applies here harder than anywhere else: since you're starting from zero files, you'll restart, add a file, restart, add a file. Batch your outfit files first, then restart once. Also note the README's seasonal mapping is a suggestion, not a rule - if you'd rather use clothing1 for "casual" and clothing2 for "formal," nothing stops you. The folder names are arbitrary; only the file format matters.