Project 04 — 2026
Wedge
A design-system conformance linter — and the product, brand, and story I built around it.
Wedge is a tool I designed and built: it scans a codebase for design-system drift — hard-coded colors, off-scale spacing, ad-hoc type — and reports it everywhere teams already look, from the terminal to the pull request. I owned the whole thing: the engine, the identity, and the pitch.
An 11-slide deck for investors and partners — thesis, moat, market, model. I wrote the narrative and designed every slide in the product’s own visual language, so it reads as an extension of Wedge, not a deck about it.
The surfaces where conformance lives — a dashboard, a marketing site, and a handoff report — on one design system: floating cards, a single amber accent, monospaced data. The same truth, legible on every surface.
The problem
Design systems decay silently. A token gets bypassed here, a spacing value hard-coded there, and six months later the system no longer describes the product. Nobody notices until it’s expensive to fix.
The approach
Wedge treats conformance as a measurable, trackable thing. It pulls your tokens from any source — including live Figma Variables — scans the code, and quantifies the drift against a budget you set.
Then it meets people where they work: a terminal summary, an inline PR comment, an HTML dashboard, a PDF for stakeholders. Same truth on every surface — so drift becomes a number a team can actually manage.
“You can’t hold a design system together with good intentions. You hold it together with a number that goes up when it breaks.”