Symbiotica Prompt Compose (deprecated — use Prompt Recipe)
Deprecated, but the byte-exact composer still does its one job
- system_prompt
The display name says it all: Symbiotica Prompt Compose (deprecated - use Prompt Recipe). The pack still ships it because older graphs reference it, but new work should go to Prompt Recipe, which does the same composition with version picks on top. That said, this node has one genuinely nice property worth understanding before you delete it from your template.
What it does
It composes one asset type's architect prompt exactly the way the queue composes it: the shared _rules/ blocks first, the type's own block last. The tail of a prompt carries the most weight, so that ordering is a deliberate choice - the type-specific block is the last thing the LLM reads, and it wins.
The panel shows the byte-exact text, which is the point: this node replaces the join-strings-and-preview scaffolding people build out of primitive text nodes, and it guarantees what you're testing is what the queue actually sends.
The inputs and output
project_path(required) - the project folder holding the prompt book. Wire the Prompt Book'sprojectoutput here.category(required) - the asset type to compose. The panel's picker lists the book's types, so you don't type it blind.system_prompt(output) - the composed architect prompt for this type. Same text Category Prompts hands the LLM for its sheets. Wire it into an LLM node to test the book against a real call.
That's the entire surface. Two inputs, one output. It doesn't call an API itself - it's pure text assembly, which is why it needs no key and no model.
Install
Same as every node in the pack:
cd ComfyUI/custom_nodes
git clone https://github.com/symbiotica-ai/comfyui-nodes.git symbiotica
pip install -r symbiotica/requirements.txt
Then restart, or just search Symbiotica in ComfyUI Manager.
Gotchas
The honest advice: don't build anything new on this node. Prompt Recipe's whole reason for existing is that this one composes without giving you a way to compare two phrasings of the same block - you'd have to edit the file between runs. Compose also has no version slots, no (follow category) mode, and no bucket handling. The main reason to touch it is debugging: if you suspect the queue is sending something other than what you think, drop this in, wire system_prompt to a preview, and compare byte for byte. For anything past that, use the Recipe.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| project_path | STRING | Client project folder holding the prompt book. Wire the Prompt Book's `project` output, or a block's `project` passthrough. | |
| category | STRING | The asset type to compose — the panel's picker lists the book's types. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| system_prompt | STRING | The composed architect prompt for this type — the same text Category Prompts hands the LLM for its sheets. |