Front-end Technical Lead & Architect. I design the front-end architecture of SaaS products and make AI-assisted development work for a whole team.
On a real-estate SaaS platform, for a fleet of independently deployed React apps.
Designed and led for a dozen apps. A deliberately small API, composition over props, and the versioning discipline that keeps one component change from breaking every consumer at once.
30+ components built on the same compound pattern
A fleet of about 13 separately deployed React apps brought into a single shell: no reload between apps, shared dependencies as singletons, and every app keeps its own deployment.
12 apps normalized in five days against an estimated two to three months; 8 already live in the shell
Agents, skills and hooks, automated PR review, CI integration, multi-repo orchestration. Most of the work is in the guardrails that stop a confident wrong answer from reaching a branch, not in the prompts.
682 agent sessions measured to find where the cost really goes
Read: I measured my token spend, then got the conclusion wrong
Front-end types derived from OpenAPI specs, auth, tracking, an app template. Migrations go through one canary repo in real CI first, then fan out to the fleet. Plus leading a team of 10+ people: conventions, upskilling, code review.
Making AI-assisted development reliable at team scale: guardrails, measurements, and humans who stay in charge.
Things that cost me a day, written down so they cost you less.
Coding-agent skills, published with their before/after evaluation.
Skills whose behaviour is a script, not prose to interpret. Each one is run against an agent without it, on the same prompts, graded by regex, and the results are published as they happened, failures included.
From web design in 2002 to technical lead.
Off screen, and education.
