badgids/comfyui-development-skills
Source-aware ComfyUI development skills that verify volatile behavior against the target install and current official upstream sources.
Use for ComfyUI HTTP APIs, WebSockets, job submission, object/node discovery, uploads/downloads, Python/TypeScript/Swift SDKs, comfy-cli, comfy-api-proxy, comfy-mcp, Cloud versus self-hosted integration, and external applications that drive ComfyUI.
Use when changing or diagnosing ComfyUI core execution, server behavior, backend APIs, model loading, caching, scheduling, node execution internals, filesystem handling, or other code owned by the ComfyUI runtime rather than a third-party custom-node pack.
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.
Use for any task that creates, modifies, debugs, validates, tests, packages, publishes, or reviews ComfyUI code, custom nodes, frontend extensions, workflows, subgraphs, API clients, SDK integrations, CI, or performance behavior. This root skill routes the task to focused specialist skills and requires live or version-matched verification before volatile ComfyUI details are treated as current.
Use for ComfyUI JavaScript or TypeScript frontend extensions, custom widgets, node UI behavior, menus, settings, dialogs, extension hooks, client-server UI integration, frontend build issues, or code that depends on ComfyUI_frontend internals.
Use when creating or editing custom-node package metadata, pyproject configuration, Registry publication, comfy-cli publishing, Manager compatibility, release automation, node-pack scaffolding, or distribution documentation.
Use for ComfyUI inference performance, benchmark design, kernel behavior, VRAM/RAM use, caching, loading time, throughput, latency, or regressions involving ComfyUI core, comfy-kitchen, or benchmark tooling.
Use ONLY when the user explicitly asks this ComfyUI Development Skills pack to maintain, refresh, or update its own upstream awareness or routing. Ordinary ComfyUI development never activates this skill automatically.
Use when creating, modifying, validating, documenting, or packaging ComfyUI subgraphs or Subgraph Blueprints, or when composing workflows from reusable graph components.
Use when adding or repairing tests, CI, workflow tests, custom-node QA, regression checks, compatibility matrices, or when deciding how to prove a ComfyUI change works.
Use when preparing changes intended for Comfy-Org repositories, aligning with current upstream architecture, reviewing RFC-related work, writing upstream-facing tests/docs, or preparing a PR-quality change for ComfyUI or related official repositories.
Use when a ComfyUI workflow fails to load, validate, queue, execute, or produce expected outputs, or when checking node availability, links, inputs, models, workflow JSON, frontend/API representation, or compatibility before execution.
Use when creating, modifying, converting, composing, templating, or programmatically generating ComfyUI workflows in frontend/editor format or API/execution format, especially when custom nodes or install-specific model options are involved.