Make a ComfyUI workflow you can reuse next week

Start with a narrow asset brief

Choose something comparable: six wall textures, three portraits or a set of inventory objects. Keep the intended game size, palette and camera view fixed while you explore the workflow.

Begin with a documented example appropriate to your installed setup. Add nodes only when you can explain the operation they perform. A huge shared graph may contain dependencies and assumptions that have nothing to do with your task.

My first goal would be a graph I can reopen and run with an intentional change, not the largest graph I can get to execute once.

Save the dependencies as well as the graph

Record the model files, relevant versions, reference inputs and important settings alongside the workflow. If custom nodes are required, note where they came from and which version you used.

A saved graph is only part of the reproducibility story. Missing models or changed node behavior can prevent the same workflow from running later. Avoid assuming that a seed guarantees identical output across different environments.

Keep an approved output with the workflow. It gives you something concrete to compare when an update changes the result or breaks a step.

Change one variable and inspect the game result

Try one controlled variation: a different material, a slightly different prompt or one reference change. Label the outputs so the comparison remains meaningful after you generate several batches.

Inspect the assets at their actual game size and against the real background. A workflow can produce beautiful large images that fail as readable icons or seamless tiles.

I'd separate generation from export preparation. Keep the high-quality source, then make the resized, trimmed or compressed game asset in a repeatable finishing step. Once that small pipeline works, expand it to another asset family instead of asking one graph to solve every visual problem at once.

Sources & further reading

• ComfyUI: workflow JSON — accessed Sep 9, 2026