For developers

BrewDocs isn't only for a brewing audience. It's also built by a software engineer, in the open, and a fair bit of what went into it is worth a look on its own. This page is for the other engineers: how the thing is put together.

Design system

Almost all of it is generated and maintained by Claude Code "agents". That works because of the investment in fundamental design patterns underneath: DaisyUI as the foundation, an extended token set on top of it, and a dash of CLAUDE.md guidance to keep the agents pointed at the right one. It doubles as a quick reference if you just want to see what's available.

Agentic engineering

The agentic setup is worth a look too: how it got to where it is, and how it ended up modularized as "Claude Team", which now gets reused across my other projects rather than living here.

GitHub

Or start at the top. The BrewDocs repo is public, and it holds everything above: the app, this site, the design system and the knowledge base.