Power Prompt File Partial

The sibling of Power Prompt Partial, for the person who wants their prompt building blocks to live in files they can edit, version, and share - not in a multiline box glued inside a node. Power Prompt File Partial loads a partial definition from a .yaml or .yml file in a dedicated folder and feeds it to a main Power Prompt node exactly like a wired partial would.

If you've ever had a characters/alice.yaml sitting in a repo waiting for a home, this is the node that gives it one. Same variables:/fragments: format, same merge rules, zero changes to how the main node consumes it.

How it works

The pack registers a power-prompt folder under ComfyUI's input directory - that's ComfyUI/input/power-prompt/ - and tells ComfyUI to treat it as a source of partial files. This node's single input, partial_file, is a dropdown listing every .yaml/.yml file in that folder. Pick one, and the node returns a partial output of type POWER_PROMPT_PARTIAL - the same socket type a wired partial outputs, so it plugs into a main Power Prompt node's include slots with no adapter.

The workflow-level benefit over the wired node is genuinely practical. Your character and style libraries become normal files: you edit them in your editor, you git add them, you share them as plain YAML, and any workflow that references the file picks up changes on the next run. The same file can back a dozen workflows without you ever copy-pasting its contents.

The pack even registers a small upload endpoint, so you can push a partial file straight from the node's UI panel instead of dropping it into the folder by hand. New files appear in the dropdown after ComfyUI refreshes its file list.

Installing it

It's part of the same "Power Prompt" pack - search that in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Kramins/comfyui-power-prompt
cd comfyui-power-prompt
pip install -r requirements.txt

Restart ComfyUI, then drop your partials into ComfyUI/input/power-prompt/. Light dependencies (pyyaml, jinja2, pydantic), no models to fetch, nothing heavy anywhere in the stack.

Where people get burned

• The file has to be in the folder. All paths resolve through the power-prompt partials directory - no absolute paths, no ../ escapes. Try to point it elsewhere and you get a "not found in the power-prompt partials folder" error. It's a deliberate sandbox, not a bug.
• The dropdown doesn't show your new file. ComfyUI caches its file lists; refresh the list (or restart) and it'll appear. If the folder is empty, the dropdown just shows an empty entry.
• The same merge rules apply as wired partials. Included files are the lowest priority in the composition - main YAML wins, wired partials win over files. And if one file's variables need to gate another file's options via when/unless, remember wired partials resolve first, so file-to-file gating is the wrong direction.

Honestly, this is the node to reach for as soon as you have two workflows sharing a prompt component. One workflow, and a single Power Prompt with everything inlined is simpler. But the moment you're maintaining the same character block in several graphs, moving it to a file here is the difference between editing one YAML and hoping you remembered every copy.