Component APIs Shape Teams
A primitive earns its place when correct composition is the easiest thing to do with it. Prop count is a side effect of that, never the goal.
Staff Software Engineer · Frontend Architecture and Design Systems
I lead frontend architecture and design systems for product teams. The job: a complex interface that stays fast and accessible while more people ship into it every week.
Independent projects and the systems I’ve built with product teams.
Reusable agent skills for the way I build software. Turns ideas into scoped tickets and carries work through implementation and review, with a fantasy theme that makes the tooling fun to maintain.
Public repository, Claude Code plugin, portable SKILL.md workflows, specialist code reviews, GitHub and Linear tracker support, PR validation and visual proof.
A terminal UI for Apple Containers. It manages the containers, images, and volumes already on the Mac, and shows the exact command before anything destructive runs.
Public repository, product site, Rust/Ratatui TUI wrapping Apple's container CLI, live telemetry, confirmed destructive actions, Homebrew and shell installers.
Fail-closed image updates for Portainer and Compose. A digest has to mature before it can be applied, and a failed health check rolls the service back and opens the breaker.
Public repository, product site, Go CLI and daemon, digest pinning, no Docker socket, circuit breaker, Git proposals that never self-merge, signed releases.
A self-hosted app for comic collectors. React UI, with flows designed for people who come back to it every week.
Public repository, product site, self-hosted product surface, state clarity, type-safe interface work.
Led the design system from beta toward general availability and owned frontend direction for CRM and Contacts, from component APIs to navigation and saved-search flows.
639+ semantic tokens, a Radix-to-Base UI migration, and snapshot releases with OIDC publishing. Primary frontend contributor on the company’s top product, used by 87,000+ agents.
Introduced Claude Code to the team and built validation skills for design-system migrations. Defined the product architecture for an AI workforce platform and demonstrated AI features to leadership.
The migration skills guarded 6 PRs with 0 fix-ups, compared with 5 fix-ups across the previous 20. An architecture proposal drew on 17 competitive analyses and reduced the platform’s object model from 10 concepts to 5.
A primitive earns its place when correct composition is the easiest thing to do with it. Prop count is a side effect of that, never the goal.
Keyboard flow, focus, contrast, and labels go into the interface spec alongside the visual work. Anything scoped as a cleanup pass after approval tends to get cut.
I use AI where it saves real time: critique, verification, migration planning, and the mechanical parts of review that eat human attention.
Staff Software Engineer for frontend architecture and design systems, on a product team that needs someone to own interface quality end to end and put AI to work inside the engineering loop.