Skip to main content
Uses

Tools & process

What I design and build with, and how a project actually goes from a first call to something live — design it, build it, ship it.

How I work

01

Discovery

It starts with a conversation. I take notes on the real problem, the constraints, and what success looks like — then turn that into a tight scope instead of a wish list.

02

Design

I design in Figma against a small token set — type scale, color, spacing, motion — so the work is consistent from the first frame. The client gets a shareable link and one or two focused revision rounds, not a hundred.

03

Build

I build it myself, 1:1 with the design — Next.js / React / TypeScript on the web, SwiftUI on iOS. Designs survive contact with real data because the person who designed them is the one shipping them.

04

Ship

Deploy, verify, measure. I care about the boring parts — performance budgets (60fps, LCP, CLS), accessibility (AA, keyboard, reduced motion), and the thing actually working in production, not just in staging.

The stack

Design
Figma · design systems & tokens · responsive / mobile-first UX · prototyping · motion design · brand & creative direction
Frontend
React · Next.js · TypeScript · Tailwind · accessibility (WCAG) · CSS & framer-motion
Mobile
Swift · SwiftUI · xcodegen
AI & Systems
Python · FastAPI · PostgreSQL · ChromaDB · Redis · MCP · LangGraph · Ollama — agentic systems, RAG, and self-healing infrastructure
Platform & Infra
Vercel · Cloudflare · Docker · macOS LaunchAgents · Sentry · CI/CD · Git
Delivery
Agile / Scrum · roadmaps & sprint planning · stakeholder management · Jira · Confluence · Asana

This site is a working sample: Next.js 16 · React 19 · Tailwind v4 · a token-driven design system · pure-CSS motion that honors reduced-motion. See the design system →

Want this on your project?

Design, frontend, and the systems underneath — owned by one person, start to finish.

Start a conversation