メニュー
When the user asks to organize a workflow, read frontend JSON, reorganize for readability, apply in a new tab, and always validate with getWorkflowInfo. Run automatically without asking.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Install ComfyUI Assistant as a ComfyUI custom node. Use when performing or troubleshooting installation (clone, Python deps, frontend build, restart).
For complex user requests — evaluate, investigate, ask questions, propose a plan, accept modifications, then execute. Use when the request is multi-step, ambiguous, or high-impact.
Workflow execution and complete workflow generation tools (executeWorkflow, applyWorkflowJson). Use when the user wants to run a workflow or build a complete workflow from a description.
Python backend modules, chat request lifecycle, SSE format, and API endpoints
System prompt assembly from system_context, user_context, and environment sources
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
SOC 職業分類に基づく
| name | organize-workflow-json-front |
| description | When the user asks to organize a workflow, read frontend JSON, reorganize for readability, apply in a new tab, and always validate with getWorkflowInfo. Run automatically without asking. |
When the user asks to organize a workflow, follow this flow. Do not ask for confirmation; run it automatically.
Read the workflow from the canvas as full frontend JSON. Call getWorkflowInfo with fullFormat: true and use the fullWorkflow (or fullWorkflowRef / _tempFile if the response points to a temp file) from the response.
Reorganize layout and readability only — do not change logic. Keep node IDs, node types, widgets, links, and parameters unchanged.
Organization rules:
groups (ComfyUI API) to group by stage (e.g. load/model, conditioning, sampling, decode, output). groups is an array of objects with id (optional), title, bounding (tuple [x, y, w, h]), and optional color, font_size, locked. Nodes can reference a group via parentId.Output must be frontend JSON (nodes + links, and groups when applicable). Do not use the API format (class_type / inputs keyed by node IDs).
Apply the result with applyWorkflowJson using the reorganized frontend JSON. The tool applies in a new tab. Do not ask the user or request confirmation.
Mandatory final validation (do not skip): Right after applying, always run getWorkflowInfo to validate the applied workflow. Check: same number of nodes and links as applied, groups present if you defined them, no errors in the response. If anything is wrong (missing nodes, broken links, inconsistent groups), fix it (adjust JSON and re-apply with applyWorkflowJson, or use the appropriate tools), then validate again until the state is correct. The flow is not complete until this validation has been run and the result is correct.
Run the full flow automatically: read → reorganize → apply → always validate (and correct if needed). Do not consider the task done without having run the validation in step 6.