Claude Code plugin
Builder
A tool that lets PMs and designers make front-end changes that stay consistent with the design system. They describe the change they want, and the plugin generates the matching code for an engineer to review before merge.
The problem
PMs and designers are often the first to spot UX and UI problems, and the best placed to solve them. Today the fix goes through an engineer, or through a codegen tool that drifts fast and loses visual consistency. Builder lets them make the fix themselves, inside the design system. The idea comes from the design-to-code workflow I built at NRC Health.
How it works
Builder scans the repo and extracts a token contract (DTCG, a standard format), validated by a human then frozen as the reference. Every change is then checked against that contract, line by line, before any commit.
Tiered by risk
T1 covers simple changes: a color, a spacing value, a label, a variant. T2 composes new UI from patterns already in the app. T3, anything involving logic, data or auth, stops with a clean handoff for the engineer. When in doubt, it always promotes a tier up, never down.
The architecture
Builder is a versioned Claude Code plugin (v0.2.1), installable from a marketplace. The orchestrator takes the request, tiers it by risk and holds the two human gates. Three agents run only when a change needs them. At the end, a validator that is plain code checks every diff: nothing off-token, project lint and typecheck green.
Where it stands
Builder is at V1 and has not been piloted yet: this portfolio is the first target, a repo on a different styling stack comes second. Its triage is tested on a set of 18 cases. It works on web apps only, native mobile is out of scope. It never commits or pushes by itself, and anything touching logic, data or auth goes back to an engineer.