Prompt Styles Selector

If you came from Automatic1111, you probably built up a styles.csv full of saved prompt presets - your go-to "cinematic," "anime," "photoreal" combos of positive and negative text. Prompt Styles Selector lets you pull those exact presets into ComfyUI. Pick a style from a dropdown and it spits out the positive and negative prompts that style is made of. It's a bridge between the two UIs, and it saves you from re-typing prompt boilerplate you already dialed in.

This is a genuinely nice piece of the WAS suite because ComfyUI doesn't have A1111's styles feature natively. The KB's ecosystem history is blunt about the tradeoff: ComfyUI has more power but A1111 is easier, and little quality-of-life features like saved styles are part of what people miss. This node claws one of them back.

How it works

There's a bit of one-time setup, and the README spells it out. On a recent build, WAS generates a was_suite_config.json file. You open it and point the webui_styles value at your A1111 styles.csv (double backslashes on Windows paths), then restart ComfyUI. Now your styles are loaded, and the Prompt Styles Selector dropdown lists them. Select one, and - in the README's words - "the first output is your positive prompt, and the second output is your negative prompt." There's also a webui_styles_persistent_update option that re-syncs from your WebUI styles file every time ComfyUI starts, so edits over in A1111 keep flowing through.

The inputs and outputs that matter

• A style selection - the dropdown of styles loaded from your styles.csv.
• A positive prompt out - the first output; wire it into your positive CLIPTextEncode.
• A negative prompt out - the second output; wire it into your negative CLIPTextEncode.

I'm naming the two outputs straight from the README's description (positive first, negative second) rather than a formal schema. The key thing is not to cross them - first is positive, second is negative.

How to install it

Part of the WAS Node Suite:

• ComfyUI Manager: search was-node-suite-comfyui, install, restart.
• Manually: cd ComfyUI/custom_nodes && git clone https://github.com/WASasquatch/was-node-suite-comfyui/, then pip install -r requirements.txt against your ComfyUI Python, and restart.

No model download - but remember the config step above, or the dropdown will be empty.

Common issues

By far the most common problem: the style dropdown is empty or the node does nothing. That's the setup step. If you haven't edited was_suite_config.json to point webui_styles at a real styles.csv and restarted, there are no styles to select. Double-check the path is correct and, on Windows, that you used double backslashes - a single-backslash path silently fails to resolve.

Second: styles are just text templates, and a style built around SD 1.5 tokens may not do much on an SDXL or newer checkpoint. The style loads fine; it just may not carry the punch it did in A1111. Treat imported styles as a starting point and re-tune for your current model rather than assuming they transfer one-to-one.

And the pack caveat: WAS Node Suite has been retired since December 2023 - used everywhere, unmaintained. If a ComfyUI update makes every WAS node vanish with an "Import Failed", that's suite-level dependency drift, not this node. Re-run requirements.txt against the correct Python environment (or the bundled install.bat) and restart.