💬 Qwen System Prompt

The system prompt is where Qwen-Edit's behavior actually gets set - it's the standing instruction that frames every edit you ask for, and a good one is the difference between "change the sofa to red, everything else identical" and the model reimagining the whole room. ArchAi3D Qwen System Prompt is a dropdown of 31 curated versions so you stop rewriting them from memory. One input, one output, no moving parts.

The preset dropdown is the whole node. The defaults worth knowing:

• Default Helper - the neutral baseline ("describe the image, then explain how the instruction modifies it, keeping consistency where appropriate"). Safe starting point for anything.
• Environment Only Scene / Scene With People - two flavors of the same reminder: people in frame change how the model handles edits, and telling it which mode you're in improves consistency.
• Maximum Consistency / Balanced Consistency / Creative Interpretation - the strength ladder. Maximum is what you want for material swaps and camera moves where the rest of the image must not drift; Creative is for when you want it to take liberties.
• Material & Texture Editor, Object Removal Expert, Object Addition Specialist, Colorization Expert, Lighting Specialist - role prompts that bias the model toward one kind of edit, useful when you're doing one type of work all day.

The optional custom_prompt (multiline) overrides the dropdown - select "None" or type your own and the node outputs that instead. One output: system_prompt, a STRING. Wire it into the system_prompt input of the pack's Qwen encoder nodes (or any encoder that takes one).

Why this matters for the pack

This isn't a fancy mechanism - it's a library. But the pack's own documentation leans on it: the "weight spike" fix in Encoder V2 was about how system-prompt text interacts with encoder strength, and these presets are the tuned versions that work with those encoders. If you're copying Qwen workflows from this pack, the System Prompt node is usually sitting right before the encoder for a reason.

Installation

Ships with ComfyUI-ArchAi3d-Qwen. ComfyUI Manager ("ArchAi3d Qwen") or:

cd ComfyUI/custom_nodes/
git clone https://github.com/amir84ferdos/ComfyUI-ArchAi3d-Qwen.git
cd ComfyUI-ArchAi3d-Qwen
pip install -r requirements.txt

Restart → ArchAi3d/Qwen/Prompts. Free personal, paid commercial license.

Where people get burned

The "None" option returns an empty string - so if you wire it straight into an encoder that expects a system prompt, you get silence, not an error. And don't stack presets: this outputs one system prompt, and if you chain two of these nodes the second just overwrites the first. Finally, these presets are written for Qwen-VL/Edit style encoders - feeding them to a stock SDXL CLIPTextEncode does nothing useful, because that path doesn't consume a system prompt the same way.