What is in it
Character consistency
One identity reference feeding turnarounds, expressions and outfit variants that stay the same person. The most-run category, and the clearest demonstration of why the structure matters.
Campaign sets
A product node feeding a hero and its crops, so one replacement updates the set in dependency order rather than orphaning half of it.
Scene and sequence
Multi-shot scenes with shared light and location, boarded on the director stage.
Style studies
The same subject through several treatments, framed identically so they are genuinely comparable.
World rules
Palette, material vocabulary and scale reference as shared nodes that locations and characters inherit.
Utility graphs
Small, unglamorous things — a batch of crops, a consistent upscale pass — that save an hour a week.
Running one
Open it
A published workflow opens as a working graph in your own canvas. It is a copy — nothing you do affects the original, and nothing the author does later changes yours.
Swap the inputs
Put your reference in the slot the author left open, and run. If it is a good workflow, that is the only step required to get something useful.
Take it apart
The interesting part is almost always the connections rather than the prompts. Follow what feeds what, and ask why the author put a clause upstream instead of repeating it.
Break it deliberately
Delete an edge and run again. What stops working tells you what that connection was carrying — this is the single fastest way to learn the tool.
Publish yours back
If you changed it into something better, publish it. Attribution to the original stays attached through the fork.
How to judge one before you spend on it
- Use count over likes
- People like things that look impressive and run things that work. The run count is the honest number and it is the one shown.
- Read the description first
- A workflow whose author says what it is bad at is almost always better than one that claims nothing is.
- Look at the shape
- A graph with one clear entry point and a shallow tree is usually well designed. Forty nodes in a chain usually means somebody never went back and tidied.
- Run it on a bad input
- Everything works on the author's perfect reference. What matters is what it does with yours.
Questions
Does running somebody else's workflow cost credits?
The runs cost what runs cost. Opening and inspecting a workflow costs nothing, so you can read the structure before spending anything.
Can I use a published workflow for commercial work?
Yes. Publishing grants the right to run and build on it, and what you produce with it is yours.
What if the author updates it after I have opened it?
Yours does not change. You have a copy, not a subscription — which also means you do not get their improvements automatically. Versioning that handles this properly is on the roadmap.
How do I get mine featured?
Publish things people run. Featuring is curated by people looking for workflows that solve one problem well, and there is no way to buy the placement.