# Design systems

Your teams will use the system, because they helped shape it.

I’ll sit down with your designers and engineers and decide what the system holds, what everything’s called, and what an agent may make up on its own. Then I’ll write down who owns the system and how it changes, so those decisions outlast any one of us.

## What you get

- Tokens, components and documentation, kept in step across Figma and code, and written so your agents build from them too
- A governance model: contribution, versioning, deprecation, and who decides
- Adoption measured, so you have a number to show whoever asks what the system is worth

## Working together

In an Embedded build, I join your team for the long haul. If you’re starting from nothing, we’ll decide what to build first. If you have a system already, we’ll find where it leaks and why your teams work around it. Then I ship product through the system with your team, agents too, and fix what breaks.

## Evidence

### Vodafone Neo

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-up: Vodafone Neo](https://phil.dev/work/vodafone-neo/)

## Say hello

Email [hello@phil.dev](mailto:hello@phil.dev). I read everything that isn’t a sales pitch.

[LinkedIn](https://www.linkedin.com/in/frontendphil) · [Bluesky](https://bsky.app/profile/phil.dev) · [RSS](https://phil.dev/rss.xml)