Command Registry — Spec Studio

Browse the tcl-registry command surface, edit every field of a CommandSpec, and render it back out as a drop-in registry .rs file or a Tcl dialect stub. Import a package's own Tcl and the compiler will infer a starting signature for each proc it finds.

Everything runs entirely in your browser. The command registry, the Tcl compiler's analyser, both renderers, and the Tcl language server itself are compiled to WebAssembly and served from this page's own directory. Nothing you type or import is uploaded — no server, no API, no telemetry. Once this page has loaded you can go offline and it still works.

One opt-in exception. The Fetch releases from GitHub panel on the Import a package tab — and only that panel — talks to the network: it reads tags from api.github.com and downloads release archives from codeload.github.com, directly from your browser, unauthenticated, and only when you fill it in and press the button. Every other way of getting sources in (drop files, pick a directory, upload .zip archives) is offline. If you would rather the page never reach the network at all, use the .zip upload path instead.

Opening a GitHub issue is the other action that leaves the page, and it is a link you click: the issue form opens pre-filled in a new tab so you can read it before posting.

Pack —

—

Registry

—

Pick a command on the left, or start a new one.

The pack's .tclspec source — the studio's one authoritative document. Every other surface is a live projection of it: edit a field in the form and this text updates; edit this text and the form, the pack list, and the collision report all follow. This is also the deliverable.

Live save is on: every edit is kept in this browser.

Write Tcl that calls your pack's commands. It is analysed with the pack installed over the shipped registry — the same installer and the same analyser the language server runs — so these are the diagnostics your editor would raise. Click any word to see which spec answered for it, the argument role, and the exact spec property that produced it.

What an editor sees

—

Diagnostics

Inspector

Click a word above.

spec pack

—

form

—

Drop a package's .tcl files here, or point at a whole library directory. Each file is compiled with the real analyser — the same one the language server runs — and every proc it finds becomes a draft spec: arity and argument roles from how the body uses each parameter, plus the shape heuristics that read the body itself — option tables from -* dispatch, -- handling, mode words that become subcommands, closed value sets, and callbacks with their appended arity. Every conclusion comes with the evidence behind it.

Drop .tcl files here, or click to choose

a package's sources, or a single script — nothing is uploaded

Add one .zip per release — GitHub's Download ZIP of a tag, a release asset, or anything else containing the package's sources. Each archive gets a version label (guessed from the file name, and editable: the labels are what every range is derived from). The importer then drafts each release independently and diffs them, so introduced_version and retired_version come from releases that actually witness the change rather than from the newest snapshot's own version number. Nothing is uploaded — the archives are unpacked in this page.

Drop release .zip archives here, or click to choose

one archive per release — nothing is uploaded

These archives are every release this package ever had. Off (the default), a command present in the oldest archive only proves it existed as far back as you looked, so no introduced_version is written for it and a note says the introduction is unknown. On, the oldest archive is the first release, so a command present there is recorded as introduced there.

Fetch releases from GitHub uses the network

This is the only part of this page that makes a network request. It fetches from api.github.com and codeload.github.com directly from your browser, unauthenticated and with no credentials attached; nothing else on this page ever uses the network. GitHub will see your address and the repository you asked about. Prefer the .zip upload above if that matters to you — it does exactly the same thing offline.