comfyui-node-datatypes

Define ComfyUI input/output data types for node interoperability.

Updated May 29, 2026
One-click install
npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-datatypes-turkeyc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comfyui-node-datatypes
Source: https://github.com/TurkeyC/Dotfiles/tree/main/private_dot_copilot/skills/comfyui-custom-node-skills/skills/comfyui-node-datatypes
Command: npx skills add https://github.com/TurkeyC/Dotfiles --skill comfyui-node-datatypes-turkeyc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ComfyUI users often struggle with inconsistent or unclear data type definitions across inputs and outputs, leading to integration errors and reuse friction.

Core Features & Use Cases

  • Supports a broad set of data types including IMAGE, LATENT, MASK, CONDITIONING, MODEL, CLIP, VAE, AUDIO, VIDEO, 3D types, and widget types.
  • Provides explicit type references, formats, and mapping guidelines to ensure node interoperability and reliable data contracts.
  • Use cases include building scalable ComfyUI graphs with well-defined data pipelines and consistent type handling across custom nodes.

Quick Start

Review the type definitions and examples to implement data-type mappings in your ComfyUI nodes.

Frequently Asked Questions about comfyui-node-datatypes

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

FAQPage Schema
How do I define custom data types for ComfyUI nodes?

ComfyUI data types like IMAGE, LATENT, and CONDITIONING are defined using explicit type references and mapping guidelines. This approach enforces reliable data contracts and consistent type handling across custom node graphs.

What ComfyUI data types are available for node interoperability?

ComfyUI supports a broad set of data types including IMAGE, LATENT, MASK, CONDITIONING, MODEL, CLIP, VAE, AUDIO, VIDEO, 3D types, and widget types for building scalable graphs with well-defined data pipelines.

Why does my ComfyUI custom node throw a data type integration error?

ComfyUI integration errors often stem from inconsistent or unclear data type definitions across inputs and outputs. Applying comprehensive type references with precise formats and validation resolves these reuse friction issues.

Can I use 3D and widget data types in ComfyUI node graphs?

Yes, 3D and widget data types are supported in ComfyUI alongside standard tensors like MODEL and CLIP. Explicit type references and mapping guidelines ensure these formats maintain node interoperability within complex graphs.

How do I validate ComfyUI conditioning and latent tensor formats?

Validating ComfyUI conditioning and latent tensor formats involves reviewing comprehensive type references with precise formats and practical usage examples. This enforces reliable data contracts and guides correct implementation.

When should I implement explicit type mappings for ComfyUI tensors?

Explicit type mappings for ComfyUI tensors are needed when building scalable graphs with well-defined data pipelines. This practice ensures consistent type handling across custom nodes and prevents integration errors from unclear definitions.