agentleFS
badgidsbadgids/comfyui-development-skills/AGENTS.md

comfyui-development-skills

AGENTS.md4 starsChanged 44 days agoMITView on GitHub

For any ComfyUI development task in this repository: Do not preload every specialist skill. The pack is intentionally routed so irrelevant ComfyUI knowledge does not consume context. Self-maintenance rule: never mutate the pack during ordinary source discovery. Activate comfyui-self-maintenance only when the current user explicitly asks to maintain or refresh the pack. Normal maintenance is limited to the machine routing registry and upstream snapshot. If broader skill knowledge is needed, the skill must present Report only / Self-modify only /…

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Read only the matching specialist skill under skills/ relevant to the task.

    line 7
  2. Very specific:

    Use skills/comfyui-development/references/source-map.md, upstream-discovery.md, and authority-policy.md to choose sources.

    line 8
  3. Distinctive:

    Verify volatile ComfyUI facts instead of trusting model memory.

    line 9
  4. Distinctive:

    Do not preload every specialist skill.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
AGENTS.md

Agent entry point

For any ComfyUI development task in this repository:

  1. Read skills/comfyui-development/SKILL.md first.
  2. Identify the compatibility target.
  3. Read only the matching specialist skill under skills/ relevant to the task.
  4. Use skills/comfyui-development/references/source-map.md, upstream-discovery.md, and authority-policy.md to choose sources. Treat the entire current Comfy-Org organization as the upstream discovery namespace, not only the curated registry.
  5. Verify volatile ComfyUI facts instead of trusting model memory.
  6. Validate before claiming completion.

Do not preload every specialist skill. The pack is intentionally routed so irrelevant ComfyUI knowledge does not consume context.

Self-maintenance rule: never mutate the pack during ordinary source discovery. Activate comfyui-self-maintenance only when the current user explicitly asks to maintain or refresh the pack. Normal maintenance is limited to the machine routing registry and upstream snapshot. If broader skill knowledge is needed, the skill must present Report only / Self-modify only / Report and self-modify / Stop, and may make broader local skill-only changes only after the user explicitly selects option 2 or 3. It still may not perform an official release, public-doc update, manifest change, test change, CI change, or publishing action.

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.