Web & Digital

walllet's designer turned its design system into code with Claude Code in ten days, then let pixel diffs and a decision log do the checking

A fintech designer had Claude Code build the design system and first flow in code; 698 pixel diffs caught two errors he had approved by eye.

Done withClaude CodeFigma

Designer's own account of his employer's product; also plugs his podcast (self-promotion)


WHAT THEY DID

Mostafa Esmaeili, the product designer behind walllet.com's Block design system, says he spent ten days in October turning it into code with Claude Code: tokens, components, icons, assets and the first product flow of the walllet.com redesign, ending on an iPhone test build.

STEP BY STEP

  1. Set up a GitHub space for the design team and split the design system into versioned repos so design system, assets and visuals stay in sync with code.
  2. Reworked components so an AI can read the files, then wrote in-house Claude Code skills (Figma file structure and dev-readiness; handoff to Expo).
  3. Split roles and added gates: no Figma change without his yes, one change at a time, and a decision log every session starts from.
  4. Wrote behaviour Figma doesn't define (sheet dismissal, toast timing, haptics, motion) as text in the repos.
  5. Had Claude run pixel diffs against Figma and treated the product flow, not the screen, as the unit of handoff, with a Ready for Development gate.
  6. Fixed every gap upstream in the repo that owns it, never in the app.

HOW IT WENT

He reports 563 commits in ten days (Claude wrote 433, he wrote 130) and 455 logged decisions. Claude ran 698 pixel checks against Figma; most components were 0.0% to 1.3% different. The first flow logged 66 gaps; 61 are closed and five are still open.

Reported results: 563 commits in ten days (433 by Claude, 130 by him); 455 decisions logged; 698 pixel checks, most components 0.0%-1.3% different; 214 component gaps on day one; first flow 66 gaps, 61 closed; first flow at v0.4.1 on an iPhone test build.

WORTH KNOWING

A dated, numbered account of where an agent-built design system breaks (behaviour Figma never defines, effects that render differently in code) and the human gates he added after Claude changed a component without asking.

TRY IT

  • Give an agent your design system and one real flow, and count the questions it can't answer from your files.
  • Write behaviour down as text: how sheets dismiss, toast timing, haptics and motion.
  • Run pixel diffs against Figma; he says they caught two errors he had approved by eye.
Read the original ↗

Rates the entry, not the tool.

Source: Mostafa Esmaeili · Muzli - Design Inspiration (Medium)Open as a page

  • Work done: Oct 2026
  • Source published: Nov 17, 2026
  • On 4TC: added Nov 18, 2026 · checked Nov 18, 2026
About this source

Type: First-person workflow · Firsthand report

  1. Design system to code with Claude Code: what 563 commits taught me
    Mostafa Esmaeili · Muzli - Design Inspiration (Medium) · Published Nov 17, 2026 (Posted late on 17 Nov 2026 PT (18 Nov UTC) in Muzli on Medium.) · Checked Nov 18, 2026
    Primary: the designer's own first-person account of his employer's product (walllet.com). Ends with a plug for his podcast (Money Design) and links his portfolio case study (self-promotion). No vendor sponsorship found.
    Access: Medium page returns 403 to scripted fetches; full text read via a page fetch and the Muzli RSS feed.
  2. Block Design System (AI-Ready Design System Case Study)
    Mostafa Esmaeili · mostafa-esmaeili.com · Publication date not stated (Undated portfolio page; project year shown as 2023-2026.) · Checked Nov 18, 2026
    Supporting: the designer's own portfolio case study of the same system (self-promotion).
    Access: open

Source check: Researched from the public page; not yet re-checked by an editor. Nobody at 4TC has tested this.

Claims and where they come from

  • In October he spent ten days turning walllet's design system into code with Claude Code, covering tokens, components, icons, assets and the first product flow of the walllet.com redesign, ending on an iPhone test build. (reported) [1]
  • 563 commits in ten days: Claude wrote 433 and he wrote 130. (reported) [1]
  • He split the system into versioned GitHub repos and wrote in-house Claude Code skills: one learns the team's Figma file structure, another runs the handoff to Expo, the React Native framework the app is built on. (reported) [1]
  • Early on, Claude removed two component slots without asking; the rules 'No Figma change without my yes' and 'One change at a time' came from that incident. (reported) [1]
  • Every call he made went into a decision log, 455 decisions in ten days, so each new agent session started from what he had already decided. (reported) [1]
  • Claude ran 698 pixel checks against Figma; most components landed between 0.0% and 1.3% of pixels different. The diffs caught glass surfaces rendering upside down and a key visual with its two source images swapped, both of which he had approved by eye. (reported) [1]
  • On day one Claude logged 214 component gaps; the first product flow logged 66 gaps, of which 61 are closed and five are still open. (reported) [1]
  • The first flow is in testing as version 0.4.1 on an iPhone test build and is not in users' hands yet. (reported) [1]
  • Fixes go into the design system repos, never the app; a missing glow and two missing icons reached the running app in under 30 minutes. (reported) [1]

4TC interpretation

Our reading, not something the source says.

His point is that the agent did not create gaps in the system; it found the ones he had been answering in person for three years. He says most of his hours went into decisions, gate reviews and the decision log rather than frames.

Designer impact

Alleged [1]

An agent can quietly change a component's contract: he says Claude removed two component slots without asking and nothing visibly broke.

  • Require a designer's yes for every change to the Figma library or component API.
  • Make one change at a time so each one can be reviewed.

Alleged [1]

Screens that look right can still be wrong: Figma paints layered effects bottom-up and React Native top-down, so glass surfaces rendered upside down.

  • Run pixel diffs against Figma instead of relying on visual review alone.

Established = documented by primary sources or the company’s own statements. Disputed = contested with evidence on both sides. Alleged = reported, not established.

Votes rate whether this entry was useful. They are not an endorsement of the tool, and don’t mean voters agree with the company’s practices.

Report an issue or correction

Share your own experience

4TC does not endorse a tool unless an explicit 4TC endorsement is shown.

Get the best of these weekly

The weekly design brief, starting soon: the most useful workflows, tool updates and developments, with sources. Sign up now and the first issue will come to you.