Every project I started, including ThinkForTreats, the IDP server, and my own portfolio, meant rebuilding the same buttons, inputs, and modals from scratch, each one slightly inconsistent and none properly accessible. Rather than keep solving the same problem piecemeal, I built Raditail: a component library with consistent theming, accessibility handled properly, and an API designed for reuse across projects instead of copy pasting. Checkout the storybook here!

I could have reached for shadcn/ui, Radix, or MUI, and for a project on a real deadline, I would. But my goal here wasn't shipping UI faster, it was proving I could make the underlying decisions myself: component API design, accessibility implementation, theming architecture, versioning. Consuming someone else's library doesn't demonstrate any of that. Building one does. Most of my recent work has been backend and infrastructure heavy, spanning Postgres, Redis, Neo4j, and Kubernetes, so Raditail is also evidence that I bring the same systems discipline to the frontend: clear contracts, composability, and consistency by design rather than convention.