Built by Connor

Change and delivery work is a long chain of documents that each depend on the last. ChangeKit runs that chain as twenty specialized agents under one orchestrator, so the output of each step arrives already shaped as the input of the next.

It started as the Gem Creation Studio: a Gem that builds Gems by interviewing the person who needs one. Most people who need a custom assistant cannot write the instruction set behind a good one, so they skip it or produce a paragraph that does not hold. Asking them questions instead — what the task is, who it is for, what a good answer looks like, where the model should refuse — and writing the instructions from the answers is what made it land.

The Reinvention Studio generalised that pattern into a platform: seven guided studios, one per artifact type, each turning a description of a repeated task into a working, governed agent. Everyone who had the Gem came across when it shipped, which is why these are one entry and one number rather than two. The pattern both proved is the one I keep returning to: the hard part is elicitation, not generation.

Paid dictation tools send your audio to a server. This one doesn't. A global hotkey opens an on-device transcription session, Apple's Foundation Models rewrite the raw transcript into clean prose, and the text lands in whatever app has focus, with your clipboard restored afterward.

Transcription wasn't the hard part. macOS filters synthetic keyboard events aimed at registered global hotkeys, so I proved the injection path and the permission-stability story in a spike before writing a line of the app.

When work crosses between people, the reasoning context shatters. Everyone re-explains the problem to their own separate session and files get couriered around. This puts both people in one room that stays lit: same session, full shared thread, each turn attributed to whoever typed it.

It runs on a single enterprise seat with no API key, which is the part that makes it deployable inside a company rather than a demo.

New Teams is a Chromium app, and Chromium caches your messages in a local IndexedDB store. The bodies are V8-serialized, a binary encoding rather than encryption. This snapshots a temp copy of that store, decodes it, and exposes the result three ways: a CLI exporter, an MCP server so Claude can read the day, and a scheduled digest.

It never opens the live database for writing, cannot send anything, and makes no network calls.

A deck becomes a branded web deck. A client brand becomes a full design kit. A morning of messages becomes a triaged work queue. Each of these was a recurring afternoon of work before it became a skill.

They compose. The brand skill feeds the deck skill, which feeds the publishing skill. That is the actual point: not twelve shortcuts, one pipeline.

A single-file container that holds an entire workspace, registered with the operating system as its own document type, so it has an icon, opens on double-click, and renders its own HTML preview.

Mostly this exists because I wanted to know what it takes to add a new file type to a computer. It turns out to be a manifest, a bundle, and a lot of patience.