⚡| My Top-10 Styles (Editor)

My Top-10 Styles (Editor) is the config side of a two-node pairing. The pack's style library is over a hundred styles deep, and scrolling a dropdown to find your favorite for the hundredth time gets old fast. This node lets you pick ten - exactly ten - and packages them as a single TOP_STYLES value that the companion My Top-10 Styles selector consumes. Set it up once, and your day-to-day workflow becomes a one-click style toggle.

The mental model: Editor = the "settings" node, Selector = the "hotkeys" node. This page is the settings.

What it does

The node is just a grid of ten style_1 through style_10 dropdowns, each backed by the full style library, each with its own gallery button (opens the visual style gallery so you can preview before you commit) and a separator. You fill in the ten slots you actually use, and the node emits a TOP_STYLES output - a comma-separated string of the ten style names. That's it. No encoding, no conditioning, no image math. It's a selection form that produces a config blob.

The input that matters

• style_1 … style_10 (COMBO) - the ten styles. Order matters only in that it maps to the ten toggles on the selector node, so decide on a stable order you'll remember.
• gallery_1 … gallery_10 - visual preview buttons for each slot.
• Output: TOP_STYLES - wire this into the top_styles input of My Top-10 Styles.

Install

It ships in the Z-Image Power Nodes pack, same install as everything else:

cd ComfyUI/custom_nodes
git clone https://github.com/martin-rizzo/ComfyUI-ZImagePowerNodes

Restart ComfyUI, or use ComfyUI Manager (search "Z-Image Power Nodes"). No pip dependencies, no model downloads - the style library ships inside the pack.

Where people get confused

The biggest gotcha is assuming this node does anything by itself. It doesn't - it only produces a TOP_STYLES value, and that value only matters if you connect it to the My Top-10 Styles selector. If you drop the Editor into a workflow and see nothing happen, that's correct behavior; the selector is the node that actually applies a style. Second gotcha: if you change your top ten, the old TOP_STYLES value can linger in a cached workflow - re-run the editor or re-connect the output to refresh. And since the Selector works on a shared top-10 list, you can have one Editor feeding several selector nodes if you want the same hotkeys everywhere. It's a boring utility node, but it's the difference between "scroll, scroll, scroll" and "one click" on every generation.