Articulate is a workplace learning platform.
As Design Engineering Lead, I sit in engineering, bridging design and development. Over the past year, I’ve built Arc: the system product teams ship on, and designers, PMs, and agents build with, while helping shape the company’s approach to AI across Engineering, DevEx, and Platform.
The system
Tokens, components, docs, and lint. One source of truth both sides use, not a library engineers work around.
- Built the foundations so product teams share color, type, space, and behavior
- Documented the system so designers and engineers work from the same rules
- Guardrailed usage in code so the system stays the path of least resistance
Design ↔ code
Figma, Claude Design, and code. Lovable was the earlier prototype path.
- Code is the source of truth. Figma tokens feed the repo, and what ships defines the system.
- Stood up Arc in Claude Design and Lovable as living canvases, keeping prototypes in sync with code and vice versa.
- Designers and PMs prototyped with real Arc components, then engineers ported that work into product.
Agents ship on it
When agents write the UI, the system has to be infrastructure they can use.
- Exposed Arc through MCP so coding agents discover the system instead of inventing around it
- Rolled agent instructions into product repos: check Arc before writing UI
- Shipped the production PRs that made that path real, so good design scales with the agents, not just faster output
Adoption
A system that is not adopted is just a library. Arc replaces the legacy system.
- Drove migration from the legacy system across product teams
- Built component tracking to snapshot current usage and measure adoption over time
- Built tooling and linting that make the new path the default
- Held the craft bar in what actually shipped, not just in the spec
And much more 👋
All of these works were deployed in production at: