comfyui-nodes

Develop and debug ComfyUI custom nodes across V1 and V3 APIs.

9|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/marduk191/qwen3_mcp --skill comfyui-nodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfyui-nodes
Source: https://github.com/marduk191/qwen3_mcp/tree/main/skills/comfyui-nodes
Command: npx skills add https://github.com/marduk191/qwen3_mcp --skill comfyui-nodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured guide for building, registering, and debugging ComfyUI custom nodes across V1 and V3 APIs, reducing boilerplate and errors.

Core Features & Use Cases

  • Comprehensive guidance on node structure, INPUT_TYPES, and node registration.
  • Templates for common node types with concrete examples for image processing and utilities.
  • Best practices for maintainable, scalable node packs and extensions.

Quick Start

Create your first ComfyUI node by following the templates and registering it with NODE_CLASS_MAPPINGS, then extend it with examples for V1 and V3 APIs.

Frequently Asked Questions about comfyui-nodes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and register a custom node in ComfyUI?

To create a custom node in ComfyUI, you define the node structure and INPUT_TYPES, then register it using NODE_CLASS_MAPPINGS. Structured templates enforce consistent attribute naming and safe UI integration for both V1 and V3 APIs.

What is the difference between V1 and V3 node APIs in ComfyUI?

The V1 and V3 node APIs in ComfyUI differ in their definitions, schemas, and registration processes. Comprehensive guidance covers both APIs, ensuring maintainable node packs and proper frontend extensions across typical use cases.

How do I debug ComfyUI custom node registration errors?

Debugging ComfyUI custom node registration involves validating your NODE_CLASS_MAPPINGS and schema definitions. Following structured templates reduces boilerplate and errors, ensuring reliable UI node integration.

Do I need frontend extensions for ComfyUI node development?

Frontend extensions are optional for ComfyUI node development. While core node structure and registration are required, the guide provides examples for safely extending UI integration when needed.

What's the best way to structure a scalable ComfyUI node pack?

The best way to structure a scalable ComfyUI node pack is to follow best practices for maintainable templates. Enforcing consistent attribute naming and structured definitions across V1 and V3 APIs prevents integration errors.

Can I use templates for image processing nodes in ComfyUI?

Yes, you can use templates for image processing nodes in ComfyUI. The guide provides concrete examples for common node types, including image processing and utilities, to accelerate node development.