Component Library

Every new build started by rewriting components we had already written. The same accordion, the same product card, the same form field — solved well once, then solved again slightly differently on the next project.

Coding agents made it sharper. They are fast, but left alone they invent their own patterns, so the output looks like nobody on the team wrote it.

A component library anyone on the team can publish to. Closer in spirit to Tailwind UI than to a locked-down design system: you find the component you need, see how it is built, and take it.

Keeping uploads open matters. A library only one person can add to stops reflecting how the team actually works within a month.

The library exposes an MCP server, so coding agents can read the components directly rather than guessing.

The result is that generated code arrives already shaped like our code — our components, our conventions, our accessibility defaults — instead of something generic that has to be rewritten by hand.