Aleph Labs · Claude + MCP · 2026 · Reza Ilham

Figma → Dev Spec

About this note

We had a month to build a bank's design system across iOS, Android, and React Native. An agent scanned Figma each day and drafted one shared API spec for all three teams to approve.

Chapter 1

The one-month clock

At Aleph Labs, we took on a project to build a design system for an Indonesian bank across iOS, Android, and React Native. The whole library had to be ready in about a month.

Figma was the visual reference, but Figma isn't a source of truth for a component's public API. If three platform teams read the same frames on their own, they invent three different sets of prop names, types, and state flags. Keeping them aligned the usual way meant hours of cross-team meetings for every component, and the schedule didn't have room for that.

Chapter 2

What the agent scanned

Every day, the agent (Claude Sonnet connected to Figma via MCP) scanned a batch of components in the design file. For something like a button, it read every variant, type, size, and state permutation on the canvas, then drafted a single technical spec defining the public API that iOS, Android, and React Native would all implement.

Chapter 3

Three approvals instead of a meeting

The agent didn't make the spec final. One lead from iOS, one from Android, and one from React Native reviewed the draft. Once all three approved it, the spec was locked and engineers built against it. We traded long alignment calls for a quick daily sign-off and shipped the design system on time.

Chapter 4

Where it sits

It follows the same rule as CatAgent and Hotreloads. Let the agent do the extraction and first draft, then put a human approval gate before anyone writes production code. More on that in my research note on human gates.