The template browser showed a placeholder gradient for all five templates
because ComfyUI looks for a thumbnail with the same basename as the workflow
JSON and there wasn't one. Adds workflows/<name>.webp for each: a 7-frame loop
of one style applied to seven different subjects, which is the product claim
stated visually rather than in prose.
Thumbnails are 400x400 rather than the source 800x800 — 64 KB each instead of
339 KB. These install onto every user's machine, and 1.7 MB of artwork on a
78 KB pack is the wrong trade for pixels that render at a couple of hundred
pixels wide.
The README gains the full-size loop and a gallery shot. Both live in assets/
and are referenced by absolute URL, so GitHub and the Registry render them
while .comfyignore keeps the bytes out of the install.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Two things wrong on the Registry listing.
The description promised "reuse it across FLUX, SDXL, and SD1.5", which reads
as though the pack only targets those three. It is model-agnostic: a style
compiles for whatever target you pick, and FLUX and Z-Image are the models the
shipped templates happen to demo. Now matches the GitHub repo description. The
same model-specific phrasing is out of the README opening and the module
docstring; the Targets section still names models, which is factual there.
The icon pointed at https://styleref.io/icon.png, which 404s — hence the broken
image on the listing. Points at the 512x512 StyleRef mark instead. Its
background is opaque white rather than transparent, so a black mark stays
legible on the Registry's dark UI.
Metadata is read from the published version, so a release is the only way for
either fix to reach the listing.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The version lived in three places and only one was enforced: pyproject (which
the Registry publishes and the release workflow checks the tag against), the
User-Agent this client sends, and __init__'s fallback for when pyproject cannot
be read. The other two could drift silently, and API telemetry would then
attribute traffic to a version nobody is running. Bumped together, with a test
that fails when they disagree.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
"Plugin" is not ComfyUI's vocabulary. What Manager installs into custom_nodes/
is a custom node pack, and what the Registry publishes is a "node" — so to
someone browsing the Registry, "plugin" reads slightly off-ecosystem, like
calling a VS Code extension an add-on. The README is the listing page, so the
wording is user-facing.
Replaces the eight occurrences with "node pack", "the nodes", or "this pack" as
each sentence reads best. "Extension" stays reserved for its narrow ComfyUI
meaning: the frontend JS registered via app.registerExtension, which is
web/styleref.js and nothing else.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The pack cited internal planning-doc items (plan P3-7, decision D1, plan
risk 9.2) that aren't public, leaving outside contributors with pointers
they can't follow. Each comment already states its reason; only the
dangling citation is removed.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Load, Apply, Facets, Reference Images, and Login nodes for loading StyleRef
creative styles into ComfyUI graphs. Zero runtime dependencies.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
