comfyui-subgraphs
Skill4 starsChanged 44 days agoMITView on GitHub
Use when creating, modifying, validating, documenting, or packaging ComfyUI subgraphs or Subgraph Blueprints, or when composing workflows from reusable graph components.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-core-runtimeSkill
- comfyui-custom-node-backendSkill
- comfyui-developmentSkill
- comfyui-frontend-extensionSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Verify every contained node against the live target when possible.
- Distinctive: line 27
Check serialization and reload behavior in the target frontend.
- Distinctive: line 33
Before calling a subgraph or blueprint complete:
- Distinctive: line 35
verify the representation against the target/current schema.
- Distinctive: line 37
verify external inputs and outputs.
- Distinctive: line 38
test serialization and reload behavior when practical.
- Distinctive: line 39
use the subgraph inside a representative workflow.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ComfyUI Subgraphs
Sources
Use current/version-matched:
- workflow/subgraph documentation in
Comfy-Org/docs; Comfy-Org/Subgraph-Blueprints;- relevant
Comfy-Org/ComfyUI_frontendimplementation; - workflow schema/source;
- live target node catalog.
Procedure
- Identify the target ComfyUI/frontend version.
- Inspect the current subgraph/blueprint representation instead of assuming fields.
- Verify every contained node against the live target when possible.
- Define clear external inputs/outputs and avoid hidden install-specific assumptions.
- Preserve stable identifiers when editing existing reusable components unless regeneration is required.
- Validate expansion/use inside a representative workflow.
- Check serialization and reload behavior in the target frontend.
Official blueprints are patterns, not a substitute for checking the current schema/runtime.
Acceptance gate
Before calling a subgraph or blueprint complete:
- verify the representation against the target/current schema;
- validate contained nodes against the target when reachable;
- verify external inputs and outputs;
- test serialization and reload behavior when practical;
- use the subgraph inside a representative workflow;
- state clearly when frontend/runtime checks could not be run.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

