I build web applications, from the first conversation to the last release.

A CLI the whole team ships through

One command, so nobody has to wait on the tech lead to deploy safely.

Syncing a theme used to need someone senior watching, because a careless push destroys work someone else owns, a client or QA editing live, that git never had a copy of. I started this on my own initiative to take that bottleneck out. It keeps the two sides of a project separate, tags a backup before it writes anything, and stops dead at a live target.

The other half is consistency. The same tool installs our coding conventions, project scaffolding and AI rules into every repository from one source of truth, so the output looks the same whoever built it. Standards that ship with the tool do not drift the way a wiki page does, and they arrive with every update instead of being remembered.

Real data, from whatever platform holds it

The frontend decides how things look. The API decides what is true.

A lot of my work is joining a custom interface to a system that already owns the data. I build the layer in between, so the platform keeps doing what it is genuinely good at and the interface owes it nothing else. Swap the backend and the interface barely notices.

From a design file to a full MVP

Every screen, every state, web and mobile.

I built the frontend of a product platform from Figma designs in React and TypeScript: responsive desktop and mobile interfaces, authentication, multi step forms, map integrations and real time chat, plus a React Native companion app alongside it.

I was building the interface well before the backend work started, so most of the time I defined the data contract. For the chat I specified exactly what I needed, which properties, and how it had to be shaped, then worked with the backend developer until the API matched. Deciding what the frontend actually needs, and saying so early, is most of what makes the rest of the build calm.