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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- comfyui-api-and-sdkSkill
- comfyui-core-runtimeSkill
- comfyui-custom-node-backendSkill
- comfyui-developmentSkill
- comfyui-packaging-and-registrySkill
- comfyui-performanceSkill
- comfyui-self-maintenanceSkill
- comfyui-subgraphsSkill
- comfyui-testing-and-qaSkill
- comfyui-upstream-developmentSkill
- comfyui-workflowsSkill
- comfyui-workflow-validationSkill
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
- Distinctive: line 24
Search current frontend source for the needed extension lifecycle or service.
- Distinctive: line 25
Prefer public/typed extension surfaces over private implementation details.
- Distinctive: line 26
If private internals are unavoidable, isolate them and document the compatibility risk.
- Distinctive: line 28
Avoid relying on widget index/order when a current named/type-safe mechanism exists.
- Very specific: line 29
Run formatting/lint/type/build checks defined by the target project.
- Distinctive: line 30
Test the behavior in the actual frontend and check browser console errors.
- Distinctive: line 31
Verify backend/frontend version assumptions if the extension exchanges custom data.
- Distinctive: line 39
create frontend-only behavior that silently breaks API execution when API compatibility is expected.
- Distinctive: line 43
Before calling the frontend change complete:
- Distinctive: line 45
verify the hook or extension API from the target/current frontend source.
- Distinctive: line 48
test any client-server contract from both sides when the feature is connected.
≈ “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.
Files
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-Templatewhen 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
- Establish target frontend version/commit where possible.
- Decide whether a frontend extension is actually necessary.
- Search current frontend source for the needed extension lifecycle or service.
- Prefer public/typed extension surfaces over private implementation details.
- If private internals are unavoidable, isolate them and document the compatibility risk.
- Preserve API-mode compatibility where possible. Direct client-server coupling should be intentional, not accidental.
- Avoid relying on widget index/order when a current named/type-safe mechanism exists; verify the target behavior either way.
- Run formatting/lint/type/build checks defined by the target project.
- Test the behavior in the actual frontend and check browser console errors.
- Verify backend/frontend version assumptions if the extension exchanges custom data.
Do not
- copy an old
app.registerExtensionexample 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.
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
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.

