Prompt Ingredient

Most "prompt" work in 2026 isn't writing a tag list - it's assembling the right phrases in the right order, and a phrase only earns its place if you can say why it's there. Prompt Ingredient is StudioDeep's version of a spice rack: curated prompt chunks you add to a recipe one deliberate ingredient at a time. Where T2V Prompt Builder assembles full shot descriptions, this node gives you the raw building blocks.

Pick an ingredient_type from nine categories - Camera Angle, Color Grade, Environment, Image Type, Lens, Lighting, Mood & Atmosphere, Shot Type, Technical Specs - then pick one of the ~90 ingredient options under it. Each option maps to a ready-made phrase like "dutch angle, camera tilted 15–20 degrees" or "low angle looking up, slightly below eye-level". The output is that phrase as a prompt string, ready to drop into a CLIP Text Encode or slot into a larger assembled prompt.

How it works

The pack ships prompt_ingredients/*.json - one file per type, each a list of {title, prompt} pairs. The node loads them at startup, and a /studiodeep/prompt_ingredients API route lets the frontend fetch the full list so the dropdowns populate live. The ingredient dropdown actually lists every title across all types, and the JS extension narrows it to the currently selected ingredient_type - so don't be confused if you see more options in the schema than in the UI; the UI is the filtered view.

There's also a custom_override field with an honest tooltip: "If non-empty, overrides the ingredient selection above." So the dropdowns are really a browsing interface - once you know you always want a teal-and-orange grade, you can type it straight in.

Output: prompt (STRING).

Installing

The standard StudioDeep route:

cd ComfyUI/custom_nodes
git clone https://github.com/studiodeep-ai/comfyui-studiodeep StudioDeep
pip install -r StudioDeep/requirements.txt

or search "StudioDeep" in ComfyUI Manager, then restart. No keys, no models, no downloads.

Troubleshooting

• Dropdown stuck on (none) - the prompt_ingredients/ folder isn't being found, usually a path problem after a manual install. Check the folder exists next to nodes/.
• ingredient and ingredient_type seem mismatched - because the dropdown lists every title, an option from another type can linger in the list until the JS filters it. It's cosmetic; the selected phrase still resolves correctly.
• Adding your own ingredient - append to the JSON files (or add a new file with a label key) and restart. Since these are just data files, the pack is trivially extensible in this direction.

The honest take: this is the node to reach for when you want consistent, deliberate vocabulary across a project - same lighting phrase on every shot - instead of free-typing and drifting. If you need full sentences with camera motion, that's the T2V Builder's job.