Skip to main content

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

Selected work

Two public walkthroughs: one design system build, one personal knowledge tool.

Both are sanitised. One shows how I rebuilt a product UI where each team had shipped their own button variant, around primitive tokens and a single Figma library. The other shows how I wire Obsidian and Claude agents into a working knowledge loop.

Skills

Where I usually help.

01

Product Interfaces

I work from a Figma frame to a TypeScript component in the same week, locking screen layout, state model, and component API in one spec before any code is written.

02

Design Systems

I build the Figma library, the token files, and the one-page 'start here' doc. Teams can adopt without booking a walkthrough call every sprint.

03

AI-assisted Workflows

I use Claude agents to turn raw research notes into specs, first-draft docs into reviewed ones, and prototype feedback into tracked tasks. The kind of work that otherwise disappears into Slack.

04

Prototype to Production

A working Figma prototype tells me what the API actually needs. I take it through component spec, implementation in React or Next.js, and a documented code review so the shipped version matches what was approved.

Notes

Short pieces I wrote after making a call worth remembering.

Implementation choices, token naming decisions, AI agent patterns. Written down so the reasoning survives the next project.

Design systems Design Systems Are Adoption Systems Teams ship a token file, a component library, and a docs site on separate sprints, then wonder why nobody uses the system. This note is about treating all three as a single onboarding moment. Interface craft Building a Toast Component A tiny component that exposes bigger choices: interruption, motion, accessibility, queueing, and API shape.

About

Eighteen years making decisions that survive the next engineer.

Since 2007, I've worked across agencies, product companies, and consulting: as a designer, frontend engineer, and the person building the design system both sides use.

Token file, Figma library, one-paragraph 'why.' That's usually what I leave behind so the next engineer can keep going without a call.

Read how I got here →

Design Engineer available for roles and consulting. Based in Franca, Brazil.

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

Get in touch