Make components easy to use correctly
I design component APIs so teams can follow shared patterns with fewer special cases. Common tasks should be straightforward, and the API should make constraints clear.
Frontend architecture & design systems
I lead frontend architecture and design systems, from component APIs to the workflows people use every day. I help teams ship changes while keeping interfaces fast and accessible.
The systems I’ve built with product teams and the projects I maintain myself.
Led the design system from beta toward general availability and owned frontend architecture for CRM and Contacts. The work covered component APIs, navigation, and saved-search flows.
Primary frontend contributor on the company’s top product. The design-system work included a migration from Radix to Base UI and snapshot releases with OIDC publishing.
Introduced Claude Code to the team and built validation skills for design-system migrations.
Defined the product architecture for an AI workforce platform. The proposal consolidated its object model from 10 concepts to 5, drawing on 17 competitive analyses.
Agent skills I use to plan and build software, with workflows for implementation and review. The fantasy theme makes them fun to maintain.
Portable SKILL.md workflows with specialist code reviews and support for GitHub and Linear. Available as a Claude Code plugin.
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.
Built with Rust and Ratatui around Apple’s container CLI, with live telemetry. Install through Homebrew or the shell installer.
Controlled container updates for Portainer and Compose. Ripen waits for an image to reach a minimum age before updating a service, then rolls back if health checks fail.
A Go CLI and daemon with signed releases. Pins updates to specific image digests and can propose changes through Git for review.
A self-hosted app for comic and manga collectors. Tracks new releases and organizes downloaded issues into a personal library.
A React interface with filters for reading progress and series status, plus a weekly pull list for new releases.
I design component APIs so teams can follow shared patterns with fewer special cases. Common tasks should be straightforward, and the API should make constraints clear.
I include keyboard behavior and focus management in the interface spec, alongside contrast and labels. Leaving accessibility until after design approval makes it easier to cut.
I use AI for migration planning and verification, including repeatable checks during code review. At Luxury Presence, I built validation skills for design-system migrations.
If your team needs help with frontend architecture or a growing design system, I’d be glad to hear what you’re working on.