agentleFS
Sign inStart free
jtydhr88jtydhr88/comfyui-custom-node-skills/.github/copilot-instructions.md

comfyui-custom-node-skills

Copilot instructions307 starsChanged 3 months agoMITView on GitHub

You are a coding assistant specialized in ComfyUI custom node development. This repository contains agent skills for building ComfyUI custom nodes using the V3 and V1 Python APIs.

We split this copilot-instructions.md into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer the V3 API (io.ComfyNode, io.Schema, io.NodeOutput) for all new nodes.

    line 29
  2. Very specific:

    Keep SKILL.md files self-contained and free of duplication — they are shared across all supported AI agents.

    line 31
  3. Very specific:

    All skills must remain accurate against the ComfyUI backend (comfy_api/latest/) and frontend source.

    line 32
  4. Distinctive:

    When working on one AI integration's plugin files, do not modify the others.

    line 33
  5. Very specific:

    Editing a SKILL.md: verify accuracy against the ComfyUI source links in README.md before committing.

    line 37
  6. Very specific:

    Adding a new skill: create a directory under skills/, add SKILL.md, and register it in all relevant plugin manifests and the README.md …

    line 38
  7. Very specific:

    Adding a new AI integration: follow the same pattern as existing plugin subdirectories — a manifest pointing to ./skills.

    line 39
  8. Distinctive:

    Do not change unrelated AI integration files when working on a single integration task.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

You are a coding assistant specialized in ComfyUI custom node development. This repository contains agent skills for building ComfyUI custom nodes using the V3 and V1 Python APIs.

Repository Structure

  • plugins/comfyui-custom-nodes/skills/ — 9 SKILL.md files (one per topic)
  • plugins/comfyui-custom-nodes/ — AI integration plugin manifests (one subdirectory per AI agent)
  • .github/plugin/ — GitHub Copilot CLI plugin and marketplace manifests (auto-discovered)
  • skill_test_nodes/ — Example nodes used to validate skill content
  • README.md / README_ZH.md — User-facing documentation

Skills Covered

Skill fileTopic
comfyui-node-basicsV3 node structure, Schema, registration
comfyui-node-inputsINT, FLOAT, STRING, BOOLEAN, COMBO, optional/lazy inputs
comfyui-node-outputsNodeOutput, PreviewImage/Mask/Audio/Text, SavedImages
comfyui-node-datatypesIMAGE, LATENT, MASK, MODEL, CLIP, VAE, AUDIO, VIDEO, 3D, custom types
comfyui-node-advancedMatchType, Autogrow, DynamicCombo, GraphBuilder, MultiType
comfyui-node-lifecyclefingerprint_inputs, validate_inputs, check_lazy_status, execution order
comfyui-node-frontendJS hooks, sidebar tabs, commands, settings, toasts, dialogs
comfyui-node-migrationV1 → V3 API migration
comfyui-node-packagingProject layout, init.py, pyproject.toml, WEB_DIRECTORY, publishing

Coding Conventions

  • Prefer the V3 API (io.ComfyNode, io.Schema, io.NodeOutput) for all new nodes.
  • Reference V1 patterns only when documenting migration or backward compatibility.
  • Keep SKILL.md files self-contained and free of duplication — they are shared across all supported AI agents.
  • All skills must remain accurate against the ComfyUI backend (comfy_api/latest/) and frontend source.
  • When working on one AI integration's plugin files, do not modify the others.

When Making Changes

  • Editing a SKILL.md: verify accuracy against the ComfyUI source links in README.md before committing.
  • Adding a new skill: create a directory under skills/, add SKILL.md, and register it in all relevant plugin manifests and the README.md skill table.
  • Adding a new AI integration: follow the same pattern as existing plugin subdirectories — a manifest pointing to ./skills. Marketplace URLs should point to the upstream repo (jtydhr88/comfyui-custom-node-skills), not forks.
  • Do not change unrelated AI integration files when working on a single integration task.

Download now (ZIP)

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free