Twelve years of design,
sharpened into systems.

I started in product design at Delaware Life and Group 1001, regulated industries where the visible interface is the smallest part of the work. Authentication systems, financial modeling tools, dual-role platforms, multi-brand design systems. Most of what mattered happened in the layer underneath.

What I kept getting stuck on was the part of those projects nobody else wanted to own: the governance layer. The token hierarchy. The composition rules that decide what belongs to the designer and what belongs to the engineer. That layer holds the whole system together and almost nobody writes it down.

Now I work mostly on systems: a PK/PD physics engine for mRNA-LNP therapeutics, an AI orchestration product (eHignite), the governance layer of a multi-brand design system. The design pedigree didn't go away. It became the thing that lets me see the system from both sides, the design intent and the engineering reality.

What I'm really drawn to is the intersection of creativity and complex systems. The work I want to keep doing: get to a source of truth, then build infrastructure on top of it that has dynamic impact. Tools and systems that help humans do their jobs better, not tools that try to replace them.

I believe in a glass box. Most AI today is black-box: input goes in, output comes out, the middle is opaque. I use AI in the opposite shape. It reveals the gaps and underlying information that lets a system function, and I build the bridges that connect everything together. The result is a complete audit of how information interacts and communicates, not a model whose reasoning you have to take on faith.

Tools I work with: Claude Code as the primary collaborator, with scoped skills and sub-agents. Python / SciPy / NumPy. Next.js / React / Tailwind. Figma / Storybook / Code Connect.

Underneath the tools: documentation discipline. I treat project docs as a maintained artifact, not a write-once file. Every note is typed (what kind of note it is), dated (when it was true), and prunable (removed when it stops being useful) so the documentation stays useful instead of rotting.

In my free time: writing sci-fi novels, painting, the ocean, farmers markets.