I design and build fast, purposeful digital products.
UI/UX developer with a frontend focus — React and Astro, enough backend to ship end to end — plus AI-assisted workflows in Claude and an Adobe design background behind every interface.
What I bring to a team.
Interfaces that survive real use
Flows, states and edge cases resolved in the browser rather than in a mockup — because I build what I design and find the gaps myself.
Frontend that stays fast
Astro and React with a bias for shipping less. Core Web Vitals treated as a design constraint, not a report you read afterwards.
Design systems teams actually use
Tokens, components and the documentation around them, so a team ships consistently without rebuilding the basics every sprint.
The designer/developer handoff, removed
Both roles in one head. No translation layer, no spec drift, no "that is not what the mockup said".
AI woven into the workflow
Claude-assisted pipelines that absorb the repetitive work — and my own MCP tooling behind them. The judgement stays human.
Let's talk
A role, a project, or just a question about how I work.
For theBuildersShaping theWeb.
Building isn't just writing code — it’s turning ideas, flows and constraints into products that perform. Design, execution and results, working together.
Websites, product interfaces and landing systems — built to perform and to last longer than the brief.
Where the work lives.
This is my presentation page — who I am, how I think and how I work.
Writing, client work and my own software — one practice, three surfaces.
My studio. Where client websites, landings and product interfaces get designed and built.
The software I build myself: accounts, hub and gen.
I came to code through design, which is why my interfaces survive contact with real users — and real deadlines.
Trained in graphic design and Adobe tooling, working day to day in React and Astro, with enough backend to wire an API myself. Lately most of my leverage comes from AI-assisted workflows: Claude does the repetitive part, I keep the judgement.
Read the full story →One call to agree what success looks like before any pixels.
Real components, real states, reviewed on a real URL.
Documented, measurable, and yours to maintain.