Design Engineer

Eighteen years turning design decisions into shipped components.

I build token systems, component libraries, and AI agent loops. The stack is usually Figma, React, TypeScript, and Claude.

See selected work Get in touch

Design system build

From diverged components to one token system.

A sanitised walkthrough of a product UI rebuild around primitive tokens, a single Figma library, and a one-page onboarding doc. Private walkthrough available.

Open work note

Personal knowledge tool

Obsidian + Claude agents as working memory.

Notes go into Obsidian; a Claude agent links, summarises, and drafts on demand. Documented as a case study so the workflow is reproducible.

Open work note

Design systems Design Systems Are Adoption Systems A short argument for treating tokens, components, documentation, and decisions as one adoption problem. Interface craft Building a Toast Component States, stacking, motion, accessibility, and API shape as a small proof of design engineering judgement.

Since 2007 I've worked across agencies, product companies, and consulting — designer, frontend engineer, the person building the design system both sides use. Token file, Figma library, one-paragraph 'why' so the next engineer can keep going without a call.

Read how I got here →

Eighteen years turning design decisions into shipped components.

Two walkthroughs: a sanitised design system rebuild, and an Obsidian-Claude knowledge loop.

From diverged components to one token system.

Obsidian + Claude agents as working memory.

Short pieces written after a call worth remembering.

Eighteen years making decisions that survive the next engineer.

Eighteen years turning design decisions into shipped components.

From diverged components to one token system.

Obsidian + Claude agents as working memory.

If your Figma library and component library have drifted apart, I can close that gap.