Two things I built that you can look at.
Both came out of my own products, and both are what I install for clients: a component registry that stays in git, and an AI engineering team that works from GitHub issues. Each page explains how it works and what the matching engagement looks like.
Work
Component Registry
One npm package per component, docs generated from the source, live examples, versions with Changesets, and a static site you can deploy anywhere. Open source under MIT.
In short
- The folder tree is the registry; a component is an npm package
- Docs, props table and changelog generated from the source at build time
- No auth, no database, no required environment variables
AI Agent Team
Six specialised Claude Code agents, the GitHub-issue workflow that coordinates them, the standards they follow, and the hooks that enforce them. Installed once as a plugin; every repository gets the same team.
In short
- UX, frontend, backend, reviewer, test and end-to-end agents, one job each
- Issues are the handoff; a person approves the design, the contract and the merge
- Hooks lint every file as it is written and keep lint configs off limits
Want one of these for your team?
Both are things I set up for clients, matched to the repository, tools and process you already have. A short call is the quickest way to find out what that would look like.