Prompt Style Save

The style library is WAS Node Suite's built-in prompt memory: a place where a positive and negative prompt pair lives under a name so a selector node can call it back. Prompt Style Save is how pairs get in. If you have a "cinematic film still" recipe - the positive that reliably gives you shallow depth of field and the negative that keeps the frame clean - you can stop pasting both every time and just name the pair once.

The habit pays off exactly like it does in AUTOMATIC1111, whose styles.csv this system can talk to (more on that in the import/export siblings). Style the shot, not the prompt: keep the library holding your looks - cinematic, product-shot, studio-portrait - and wire the selected pair's strings into the positive and negative text encoders.

The three inputs

• name - what the style is called in the selector menu. Leave it empty and the name is generated from the first few words of the prompt, which is convenient but means you'll probably want to type one.
• prompt - the positive prompt to store, as plain STRING: cinematic film still, shallow depth of field, highly detailed.
• negative_prompt - the negative half of the pair. Saving a negative you trust is genuinely half the value here; your best negative is a thing you don't want to retype from memory.

Saving over an existing name replaces what it held. A pair already in the library under another name is left where it is rather than stored twice - the node won't silently duplicate your library.

Outputs

name is the name the style was stored under (the generated one if you left it blank). positive_string and negative_string echo back exactly what was stored, ready to wire into a positive and negative CLIP Text Encode. Those echo outputs are useful mid-setup: you can save a style and immediately see what the selector will hand downstream.

How the library is stored

Styles live in was_state.db - the pack's SQLite state file under <ComfyUI user dir>/was-node-suite/ - alongside the Noodle Soup Prompts terminology. Because it's a file beside your config, it survives pack updates, and moving machines means moving that file or using the export node. There's also a styles.json beside it that is imported into the library each time it changes and is never written to - the pack treats it as a read-only seed you can hand-edit and have picked up.

The complete loop is: Prompt Style Save here, pick with the Prompt Styles Selector node, back the whole thing up with Prompt Styles Export, and bring a library back (or migrate from A1111) with Prompt Styles Import.

Installing

Prompt Style Save is part of WAS Node Suite v3. Install via ComfyUI Manager (search WAS Node Suite v3) or:

cd ComfyUI/custom_nodes
git clone https://github.com/WASasquatch/was-node-suite-comfyui

Restart after. You need ComfyUI 0.14.0+ and Python 3.10+; nothing extra installs, because the v3 pack's rewrite runs entirely on what ComfyUI already ships. That's a deliberate fix for the v2 suite, which depended on a stack of packages that broke whenever ComfyUI updated.

One honest note: styles are strings, not models. Saving a style stores the prompt pair - it won't remember your sampler, steps or CFG. If you want the full recipe preserved, that's what a workflow file is for.