Project 04 — 2026

Wedge

A design-system conformance linter — and the product, brand, and story I built around it.

Role

Design · Build

Timeline

2026

Scope

Product · CLI · Brand · Deck

Context

Independent

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.

IdentityMark · Accent · Wordmark

The identity, built alongside the engine — one mark, one accent, one wordmark.

Twin-wedge mark — two wedges to a seam, one notch of daylight where the system holds. #E7A13B #0E0F10

The artifactsSame truth, every surface

Fig. 01 — Report

The drift report — conformance made legible across surfaces.

Wedge drift report — findings summary and token table

Wedge CLI terminal output — **Fig. 02 — Terminal.** CLI output — where engineers already live.

Wedge pitch deck slide — **Fig. 03 — Deck.** The pitch — platform & market narrative.

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.”