Relay & UIX
Personal dev infrastructure I built because I needed it to exist
Role
Sole builder
Relay and UIX aren't client work or product work — they're infrastructure I built because the tools I needed didn't exist in the shape I wanted. Both have quietly done a lot of the heavy lifting behind everything else in this portfolio.
Approach
Relay — a terminal that survives redeploys
relay-server bridges a real PTY session over the network with a native C component, exposed through an MCP server so it plugs into agent workflows directly. relay-pty was split out as a standalone session service specifically so a relay-server redeploy no longer kills active sessions — the kind of reliability detail that only shows up after the first time it goes wrong.
UIX — closing the design-to-code gap
uix-core takes Figma files and generates real component code via Gemini, rather than static markup — built to cut the translation tax between a design file and a working interface. UIX and UII-Engine extend that pipeline further.
Built for one user, hardened like it wasn't
Both tools were built for my own daily use, which forced a different kind of rigor — no support team to lean on, so failure modes had to be designed out rather than documented around.
Outcome
Both tools remain in active daily use and have materially sped up how I build every other product in this portfolio.
Next project