Web & Digital

Kargul Studio: Claude Code edited a 490-screen Figma file directly, with a rule file and an audit after every batch

A studio had Claude Code build screens directly in a 490-screen Figma file, and used a scripted audit after every batch to catch what screenshots hid.

Done withClaude CodeFigma

Studio founder's own account of designing the studio's own product (self-promotion)


WHAT THEY DID

Marcel, founder of Kargul Studio, says the team is designing Underlay, its own all-in-one workspace for agencies, at 490 screens (244 desktop frames, 246 mobile frames). Designers owned every screen and the product lead wrote a 24-page brief; Claude Code worked inside Figma through the plugin API, editing the file directly.

STEP BY STEP

  1. Product lead wrote a 24-page brief; designers owned every screen.
  2. Claude Code worked inside Figma through the plugin API, building screens when designers asked and fixing what they caught.
  3. Colours: foundations (244 variables), one brand colour on a 12-step theme scale, and purpose-named tokens; the agent only binds to tokens.
  4. Every decision went into one file, design-system.md, one sentence each with the reason and the date; every session starts from it.
  5. Designers drew real screens first and named six recurring mobile blocks (list card, sheet, form sheet, dock, bottom bar, empty state).
  6. After every batch, Claude runs the same audit script over the whole file; each correction becomes a rule, an audit check where possible, and is applied to every screen already drawn.

HOW IT WENT

He reports one audit pass over the contracts section (7 screens) caught 112 icon vectors with the wrong stroke weight, and another found clip incorrectly set on 858 frames. One correction, "pull the gaps to 8px", became a written rule and updated 59 buttons across all mobile pages.

Reported results: 244 desktop and 246 mobile frames; the meetings module alone has 44 mobile screens. One audit pass caught 112 icon vectors with the wrong stroke weight, another found clip wrongly set on 858 frames; one correction updated 59 buttons. He says designers stopped hunting for pixel problems.

WORTH KNOWING

A concrete, numbered account of what goes wrong when an agent edits a real Figma file (black fallback colours behind tokens that looked fine in screenshots), and the four files and checks the team used to fix it.

TRY IT

  • Bind every colour to a Figma variable and tell the agent never to type a hex value.
  • Keep one markdown file of design decisions, one sentence each with the reason and the date, and start every agent session from it.
  • After each batch, run a check for what screenshots can't show, such as variable fallback colours, raw hex, text styles and clipping.
Read the original ↗

Rates the entry, not the tool.

Source: Marcel (@marcelkargul) · XOpen as a page

  • Work done: not stated in the source (Not stated. The post describes ongoing work on Underlay; no start or end dates are given.)
  • Source published: Nov 16, 2026
  • On 4TC: added Nov 17, 2026 · checked Nov 17, 2026
About this source

Type: Documented method · Firsthand report

  1. how we use AI agents for product design in 2026.
    Marcel (@marcelkargul) · X · Published Nov 16, 2026 (Posted 2026-11-16T20:44:48Z (12:44 PM PT, Nov 16).) · Checked Nov 17, 2026
    Primary: the studio founder's own X Article about the studio's own product, Underlay (his bio: 'Founder @kargulstudio ... Building @tryunderlay'). Self-promotion; X paid_partnership flag false; no vendor sponsorship found.
    Access: X Article; read in full via the X API.

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

  • Kargul Studio is building Underlay, its own all-in-one workspace for agencies (projects, tasks, chat, invoices, contracts, meetings), at 490 screens across desktop and mobile. (reported) [1]
  • Designers owned every screen, the product lead wrote a 24-page brief, and Claude Code worked inside Figma through the plugin API, editing the file directly. (reported) [1]
  • Figma stored a black fallback colour when Claude bound variables; it looked fine in screenshots because screenshots resolve variables. (reported) [1]
  • Every decision goes into one file, design-system.md, one sentence each with the reason and the date, and every new session starts from it. (reported) [1]
  • One audit pass over the contracts section (7 screens) caught 112 icon vectors with the wrong stroke weight; another found clip incorrectly set on 858 frames. (reported) [1]
  • The correction "pull the gaps to 8px" became a rule that updated 59 buttons across all mobile pages and added an audit check. (reported) [1]
  • The file has 244 desktop frames and 246 mobile frames; the meetings module alone has 44 mobile screens. (reported) [1]
  • He says Claude handled the volume and did not make a single design decision. (reported) [1]

4TC interpretation

Our reading, not something the source says.

The studio's point is that the fix wasn't better prompts but files: variables-only colours, one decision file with a reason and date per rule, named blocks drawn from real screens, and an audit script run after every batch. He says Claude handled the volume and did not make a single design decision.

Designer impact

Alleged [1]

Agent output can look right in screenshots while the file is wrong: the studio says Figma stored black fallback colours behind bound variables, which screenshots hid because they resolve variables.

  • Open the actual file, not just agent screenshots, before accepting a batch.
  • Automate a fallback-colour and raw-hex check after every batch.

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.