Colophon
Building this portfolio with three agents
A note on how this site was set: one odd design reference, a Paper file, two coding agents, and a DNS change performed by a coworker who lives in a browser tab.
Last verified . Agent products and hosts move fast, so details here may be stale. Check the primary sources before you build.
The moodboard for this site had exactly one thing on it: ciggies.app. I liked how plain and collectible it felt, objects presented directly, nothing wrapped in a product story. That instinct carried straight over. These MCP apps are small production tools, and the page that holds them should feel like a shelf of real things.
So each app appears as a deck of its own widget screenshots, and the screenshots are real. The states are the point: the preview, the typed draft, the sent message, the selected range, the applied change. A hero image would flatten all of that into marketing. The deck lets you flip through what the tool actually does, one state at a time.
The artifact is not a mockup. It is the UI the model calls, and a person still has the final click.
The order of operations
Design gets decided in Paper, then translated
The design lives in a Paper file, and every meaningful change lands there before any code does. Layout, spacing, and captions get decided visually, by looking at them, so the code becomes a translation of a finished decision. Anyone who has built a site with an agent knows the alternative: the design ends up being whatever the code happened to produce, and you learn to like it. The Paper file is what has kept this site honest.
The crew
Claude Code kept the shape; Codex did the chores
Claude Code orchestrated the project. It split the work into small pieces, held the overall shape of the site together, and guarded the one constraint I refused to negotiate: no build step, just HTML, CSS, and a little JavaScript.
Codex implemented pieces of the site and picked up the operational work, which is a polite way of saying it changed my Squarespace DNS records through a browser session in Arc. I want to give that moment its due. Watching an agent write code feels normal now; code can be diffed, reviewed, reverted. Watching one drive a live browser and edit the records that decide where this domain points is a different feeling. It is also the most honest preview I have had of where this goes: a coworker with limited permissions, handed a small and well-defined task, working in the same interfaces I would have used myself.
The three apps themselves run on Railway behind WorkOS auth and ship real widgets into Claude, ChatGPT, and Codex. Every one of them follows the rule the screenshots keep showing: draft, preview, prepare, never silently send or apply. This portfolio is the smallest useful surface I could build around that rule. A shelf, some real things on it, and a person with the final click.