A private, shadcn-CLI compatible registry with its own docs site. Same workflow you already know — just yours, and zero npm publish trauma.

One canonical theme. 159 tokens across 13 families. Token names are immutable; values bend per project through a 3-tier override system. Adults, all around.

Shareable AI agent skills for coding agents. No vibes-based authoring — the agent either passes the test suite or it doesn't graduate.

A personal Next.js starter with AI agent integration baked in. The traditional “configure ESLint for two days before writing a line” phase has been canceled.

Open-source library for two-way comms between a container app and iframe apps. Iframes are an architectural mistake we collectively decided to keep. This makes that decision survivable.

A small JS/TS logging library with configurable export targets. Does one thing. Does it well. Refuses to be a framework, a plugin ecosystem, or a Discord server.

A pipeline for managing, publishing, and distributing design assets so designers ship once and every frontend engineer consumes the same source. The “hey can you re-export that SVG one more time” Slack thread dies a peaceful death.

A compound-pattern component library used across 10+ internal apps. Every component maps to a design token. The great hex-code wars end in a token table no one is allowed to argue with.

A package ecosystem of component kits, utility functions, and API integration modules — the thing every frontend project quietly depends on. Setup went from “block out a sprint” to “block out a coffee.”

A drag-and-drop platform that lets non-technical staff build internal tools without writing code. PMs ship their own dashboards now and discover, firsthand, the joy of fixing their own bugs.

The frontend deployment architecture for a logistics company's internal apps. The kind of infra that runs at 3 AM, never pages anyone, and gets exactly zero credit for it.