Hi, I’m Phil.
Day one or year five, I’ll build the thing with you, write the decisions down as we go, and stick around until that’s how everyone works, agents too.
Your agents will work the way your team does.
Giving everyone a chat window is a fair first step. Next, I’ll help you write the specs and skills that let agents take on real work.
How I work with agentsYour teams will use the system, because they helped shape it.
--color-accent#0b7a7c#2bc4b1--space-41rem--radius-md0.75remAn agent can draw a component in minutes now. So I spend my time with your designers and engineers, agreeing the tokens and the rules, and measuring adoption.
How I build design systemsYour product ships, and your team knows it inside out.
I join your team as a senior or lead engineer, from prototype to production. Tests and monitoring go in from the start, so launch day is calm.
How I ship
Many product teams were each building their own UI, so brand and accessibility had drifted apart. I came in as the first engineer on a team of designers, and built one system with them, joining Figma to code: the tokens, a React component library and the documentation.
Read the write-upAn environmental consultancy needed a Japanese-language site they could edit themselves, without losing the typography or the speed. I kept every page prerendered and put WordPress behind the build, so they can publish without a developer.
99 mobile Lighthouse score on the home page, up from 61
Read the write-upAgents wrote nearly all of this site’s code, and I reviewed it. They built it from issues I’d triaged with them and decisions I’d written down first, and I ruled on whatever they couldn’t decide.
109 pull requests in the build’s first week
Read the write-upWhat I’ve learned on the job, written down to share.
I’m writing the first ones now, and they’ll be here soon.
Available from October 2026. Currently thinking about what a team’s agents should read before they write any code.
Updated
Email hello@phil.dev. I read everything that isn’t a sales pitch.