comfyui-custom-node-backend
Skill4 starsChanged 44 days agoMITView on GitHub
Use when creating, modifying, migrating, debugging, or reviewing ComfyUI Python custom nodes or custom-node packs, including schemas, execution methods, registration, inputs/outputs, validation, caching/change detection, UI results, dependencies, and node-pack structure.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-core-runtimeSkill
- comfyui-developmentSkill
- comfyui-frontend-extensionSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 10 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
If the comfyui-development router skill is installed, apply its compatibility and source-authority policy.
- Distinctive: line 35
Do not turn a small bug fix into a migration unless migration is necessary.
- Distinctive: line 43
Do not assume the current or legacy custom-node definition style from memory.
- Very specific: line 47
If using a versioned comfy_api, inspect which versions actually exist in the target and what the official docs call stable/development …
- Distinctive: line 53
Search current official source for a comparable built-in node or datatype.
- Distinctive: line 54
Verify input/output type semantics from current target source.
- Distinctive: line 56
Keep execution logic independent of UI assumptions where possible.
- Distinctive: line 57
Add validation/change-detection behavior only when it is required and verify its current contract.
- Very specific: line 58
If dependency isolation is part of the design, inspect the current pyisolate contract and the target ComfyUI integration before inventing a …
- Very specific: line 59
If frontend behavior is needed, also use the comfyui-frontend-extension skill rather than guessing JS hooks.
- Distinctive: line 63
Run a minimal representative workflow when feasible.
- Distinctive: line 71
When supporting multiple ComfyUI generations, make compatibility behavior explicit and testable.
- Distinctive: line 79
Before calling the node or pack complete:
- Distinctive: line 85
run a minimal representative workflow when practical.
≈ “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 Custom Node Backend
If the comfyui-development router skill is installed, apply its compatibility and source-authority policy. In all cases, read the relevant current custom-node documentation before implementation.
Source set
Use as needed:
- the target ComfyUI checkout and live node catalog;
Comfy-Org/docscustom-node documentation;Comfy-Org/ComfyUIbundled/current node examples andcomfy_apiimplementation;Comfy-Org/cookiecutter-comfy-extensionfor current project/package conventions;Comfy-Org/pyisolatewhen dependency conflicts, isolated extension environments, subprocess/RPC isolation, sandboxing, or cross-process tensor sharing are relevant;- target pack source and tests;
- official test/QA tools.
First classify the work
Determine whether this is:
- a new node in a new pack;
- a new node in an existing pack;
- a bug fix;
- a compatibility fix;
- an API-generation migration;
- a packaging/import problem;
- a backend half of a frontend-connected extension.
Do not turn a small bug fix into a migration unless migration is necessary.
Current official agent guidance
If the target workflow uses comfy-cli or its installed agent skills, inspect the current/version-matched comfy-cli skill set before relying on CLI-specific custom-node advice. Its bundled custom-node guidance is useful operational synthesis, but verify node API contracts against the target ComfyUI source/docs and live registration. Do not copy that upstream skill into this pack.
Node-definition rule
Do not assume the current or legacy custom-node definition style from memory.
For a new node, inspect current official guidance and target compatibility requirements. For an existing node, identify the style already used by the project and whether its supported ComfyUI range requires it.
If using a versioned comfy_api, inspect which versions actually exist in the target and what the official docs call stable/development before choosing an import.
Implementation procedure
- Inspect the repository structure, dependency metadata, and existing nodes.
- Identify the target ComfyUI/API generation.
- Search current official source for a comparable built-in node or datatype.
- Verify input/output type semantics from current target source.
- Implement node schema/registration using the target's real contract.
- Keep execution logic independent of UI assumptions where possible.
- Add validation/change-detection behavior only when it is required and verify its current contract.
- If dependency isolation is part of the design, inspect the current
pyisolatecontract and the target ComfyUI integration before inventing a custom isolation mechanism. Do not assume the target uses pyisolate merely because it is an official project. - If frontend behavior is needed, also use the
comfyui-frontend-extensionskill rather than guessing JS hooks. - Add focused tests.
- Load the node in ComfyUI and confirm it registers.
- Inspect the live node definition and compare it with the intended public interface.
- Run a minimal representative workflow when feasible.
Registration gate
A Python file importing successfully is not sufficient. Confirm the node pack is actually discovered and the intended nodes appear in the running target.
Compatibility gate
When supporting multiple ComfyUI generations, make compatibility behavior explicit and testable. Do not use broad exception swallowing to make imports appear compatible.
Packaging handoff
For Registry/Manager packaging or publishing, also use the comfyui-packaging-and-registry skill.
Acceptance gate
Before calling the node or pack complete:
- confirm the intended node registration contract against the target ComfyUI generation;
- pass focused tests for the changed behavior;
- load the pack in the target when practical and confirm the intended nodes register;
- compare the exposed live node interface with the intended inputs and outputs;
- run a minimal representative workflow when practical;
- state clearly when a live registration or workflow check 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.

