Personal work · Built for myself
What I build when no one's asking.
Without a client or a deadline, the only bar left is whether I actually want to use the thing, which turns out to be a higher bar than most briefs set. These get the same finish I bring to the work I ship for teams.
- 01 Rudiment UI Component library Accessible component primitives, built in public An open-source React component library and companion guide covering architectural decisions, a three-tier token system, intrinsic layout primitives, accessible components with React Aria, Storybook docs, testing, and npm distribution. 3-tier token system
- 02 Token Adventure Arcade game · Teaching tool A playable coding arcade that teaches design tokens Twenty sectors of the W3C Design Tokens Format (2025.10), where you write real tokens in a CodeMirror editor, run them in a sandboxed iframe, and clear the wave when a serializable assertion engine grades your code against the spec. A hard spec turned into something you actually want to finish. Real sandbox + assertion engine
Why these are here
Side projects are where the finish shows.
When nobody is asking for it, nobody is around to talk you out of sweating the last ten percent.
The empty states, the focus order nobody will notice until it is wrong, the assertion engine that has to grade a spec honestly instead of generously. That last ten percent is the work most people skip, and it is exactly the part I bring to the products I ship for teams. Want the client case studies instead? They live on the projects page.
Open to roles
The same instinct, on the clock.
What I do for fun is what I do for teams: own the whole thing, wire the live services, and ship it finished. If that's the engineer you need, send a note.