agentleFS
badgidsbadgids/comfyui-development-skills/skills/comfyui-frontend-extension/SKILL.md

comfyui-frontend-extension

Skill4 starsChanged 44 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 10 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search current frontend source for the needed extension lifecycle or service.

    line 24
  2. Distinctive:

    Prefer public/typed extension surfaces over private implementation details.

    line 25
  3. Distinctive:

    If private internals are unavoidable, isolate them and document the compatibility risk.

    line 26
  4. Distinctive:

    Avoid relying on widget index/order when a current named/type-safe mechanism exists.

    line 28
  5. Very specific:

    Run formatting/lint/type/build checks defined by the target project.

    line 29
  6. Distinctive:

    Test the behavior in the actual frontend and check browser console errors.

    line 30
  7. Distinctive:

    Verify backend/frontend version assumptions if the extension exchanges custom data.

    line 31
  8. Distinctive:

    create frontend-only behavior that silently breaks API execution when API compatibility is expected.

    line 39
  9. Distinctive:

    Before calling the frontend change complete:

    line 43
  10. Distinctive:

    verify the hook or extension API from the target/current frontend source.

    line 45
  11. Distinctive:

    test any client-server contract from both sides when the feature is connected.

    line 48

≈ “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.

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

ComfyUI Frontend Extension

Frontend APIs move. Search current target/current Comfy-Org/ComfyUI_frontend before using any hook, service, type, or internal module path.

Sources

  • target/current Comfy-Org/ComfyUI_frontend;
  • Comfy-Org/ComfyUI-React-Extension-Template when React/TypeScript extension scaffolding is relevant;
  • frontend/custom-node docs in Comfy-Org/docs;
  • current core frontend extensions as implementation examples;
  • the target custom-node pack's existing web assets;
  • frontend tests/build configuration.

Procedure

  1. Establish target frontend version/commit where possible.
  2. Decide whether a frontend extension is actually necessary.
  3. Search current frontend source for the needed extension lifecycle or service.
  4. Prefer public/typed extension surfaces over private implementation details.
  5. If private internals are unavoidable, isolate them and document the compatibility risk.
  6. Preserve API-mode compatibility where possible. Direct client-server coupling should be intentional, not accidental.
  7. Avoid relying on widget index/order when a current named/type-safe mechanism exists; verify the target behavior either way.
  8. Run formatting/lint/type/build checks defined by the target project.
  9. Test the behavior in the actual frontend and check browser console errors.
  10. Verify backend/frontend version assumptions if the extension exchanges custom data.

Do not

  • copy an old app.registerExtension example without checking current hooks/types;
  • monkey-patch global prototypes when a supported extension hook exists;
  • assume LiteGraph internals are stable public API;
  • duplicate backend state in the frontend unless necessary;
  • create frontend-only behavior that silently breaks API execution when API compatibility is expected.

Acceptance gate

Before calling the frontend change complete:

  • verify the hook or extension API from the target/current frontend source;
  • pass the relevant build, type, lint, or focused test command when available;
  • confirm the extension registers or loads in a compatible frontend when practical;
  • test any client-server contract from both sides when the feature is connected;
  • state clearly when browser/runtime verification could not be run.

Download now (ZIP)

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.