Raptive Community
Design Infrastructure

0→1 development environment, built solo in 4 weeks. Enabled design, engineering, and product into one continuous loop

ROLE

Staff Product Designer & Design System Owner. Architecture, tokens, governance, research, build.

SCOPE

End to end design infrastructure supporting 12 to 15 engineers. Owned governance, motion, and the platform's first research practice.

TEAM

Design, Product, and Engineering

Problem

The design system was in a Figma file. No shared environment, no live review surfaces, one designer supporting 12 to 15 engineers and 2 product managers. Teams were building their own prototypes and handoff became sequential. I built the environment to keep the feedback loop continuous.

Approach

01

Aligned tokens to production

224 tokens matched 1:1 with production, built with engineering during the Figma phase. Primitives underneath, semantic aliases on top: components bind to roles, never a hex. A new visual direction ships as one token swap; the new Raptive language is staged now.

02

Close the loop

Every prototype exports from the environment into Figma, our review tool and source of truth, a debate I settled against my own artifact. CI and engineering's AI agents keep design and production current.

03

Governance so teams can ship

45 components and 26 patterns, grown feature by feature. 15 YAML governance contracts with usage rules and escalation paths, plus traceability attributes on every component. Engineers and PMs build inside the system without me in the room.

04

Pilot on real product

Creator onboarding was the first surface through the full system, and it carried the platform's first structured usability testing. The pilot tied the infrastructure to outcomes leadership cares about: an internal system connected directly to pageviews and DAU.

Results

BUILD TIME

4 weeks, solo, on github

SCALE

224 tokens, 45 components, 26 patterns, 12 prototypes

DESIGN DEBT

Full rebuild reduced to one token swap