Version-Pinned Developer Reference

[FrostySDXL]

https://github.com/FrostySDXL/comfyui-starchart

What This Repository Is

ComfyUI StarChart is a version-pinned, source-extracted companion reference for ComfyUI developers. It publishes:

a self-hostable Astro Starlight documentation site

extracted JSON artifacts for selected ComfyUI API, hook, and schema surfaces

repo-local maintainer tooling for refresh, verification, and publication

This repository is not the official ComfyUI documentation. Use docs.comfy.org for authoritative official guidance.

Background

I created ComfyUI StarChart because ComfyUI has a real developer-documentation gap.

There is plenty of ComfyUI content on the internet, but much of it is hard to trust as a development baseline. Reddit threads can be helpful but scattered. YouTube videos can show a workflow but often age badly. Community repos may solve one narrow problem, then stop updating. Even the official docs, while important, are not trying to be a version-pinned, machine-readable developer reference for every tooling and contribution task.

That leaves developers in a frustrating spot: if you want to contribute to ComfyUI, build against it, or verify how a surface changed, you often end up manually diffing source, chasing outdated examples, and reconstructing context from multiple places.

StarChart is my attempt to make that workflow less fragile.

The core idea is simple: pin upstream versions, snapshot the relevant source, extract structured artifacts from those snapshots, and publish docs that stay tied to evidence instead of memory. That makes it easier to answer questions like:

Is there a new hook?

What changed about that hook?

What is different in the pinned core compared with the previous baseline?

Which route, schema field, or extension surface actually changed?

Where should a developer start for custom nodes, extensions, integrations, or runtime metrics work?

I also built this with agents in mind.

One of my recurring frustrations was that I like using agents, but there was no single resource I trusted to give them precise, bounded, evidence-backed ComfyUI development context. Most web material is written for humans to skim, not for an agent to query conservatively. Agents do better when the surface is structured, stable, and explicit about what is guaranteed versus best-effort.

ComfyUI StarChart gives them that surface:

canonical JSON artifacts for pinned API, hook, and schema data

a merged support index for docs routing and tooling-task discovery

stable published paths and checksums via manifest.json

start-here docs for task routing

In practice, that means an agent can more reliably answer questions such as:

how do I create a custom node against this pinned baseline?

where should I look to build an extension?

what changed between two known versions?

which doc page is the right next read for metrics capture, route work, or schema validation?

The long-term goal is bigger than a readable docs site. I want StarChart to be a useful working substrate for both humans and agents: something you can inspect, diff, route through, and build on without depending on vague memory or unstable community breadcrumbs.

Who This Repo Is For

Consumers building custom nodes, extensions, integrations, or tools

Agents using the tooling schema, merged support index, and JSON artifacts to route, inspect, and interact with the repo's published developer surface

Contributors editing docs, examples, or other hand-authored content

Maintainers running verifiers, refreshes, artifact publication, or CI/workflow changes

Send your agent at it, or check it yourself, to see how easy it is to scaffold a ComfyUI-related project!

https://github.com/FrostySDXL/comfyui-starchart