System Prompt (Creepybits)

This is the pack's house system prompt, served up as a node. Feed it your rough idea and it prepends a long, pre-written brief that turns whatever LLM reads it into an "expert AI prompt engineer" - one tuned specifically for generating prompts for Flux with t5-xxl, designed for the Gemini 2.0 era. Same pattern as the Scene Director node, but for general prompt crafting instead of cinematic composition.

It's the base layer of the "AI Creative Council" in the Creepybits suite: your idea goes in, the professional briefing goes with it, and an LLM does the writing.

How it works

At startup, the node reads system_prompt.txt from the pack's assets/prompts/ folder and keeps it in memory. When you run it, it concatenates that fixed text with whatever you typed into text_2 and returns the whole thing as one string. No AI here - it's a loader and a glue node. The intelligence comes later, when you feed the combined string to an LLM.

One thing to know about the bundled text: it's written to be explicit about not censoring prompt descriptions. The file argues that since it only generates text prompts and not images, it should describe anything - including NSFW material - without filtering. That's the author's design choice, baked in. If that's not how you want your workflow to behave, edit the file.

The input and output

• text_2 - your idea or dynamic prompt text (multiline).
• Output: text - the full system brief plus your input, meant for an LLM's system prompt slot.

In the pack's own example flow: Master Key (your idea) → System Prompt node → Gemini API node → final prompt. That's the pattern this node was built for.

Installing it

Ships with ComfyUI-Creepy_nodes:

cd ComfyUI/custom_nodes
git clone https://github.com/Creepybits/ComfyUI-Creepy_nodes

restart, and it appears under Creepybits/Prompt. Or install via ComfyUI Manager, searching "Creepy_nodes". No downloads beyond the pack itself.

Where it bites

The file is read once, when ComfyUI starts. Edit system_prompt.txt and you must restart before the node sees the change - a classic "I changed it but nothing happened" moment. Also remember this is a long system prompt, so every run through an API LLM costs tokens for the whole brief. And since the same file backs this node specifically, don't confuse it with the pack's other prompt nodes: each one reads a different file, and they don't share edits.