Motion & Video · Web & Digital

A product design lead built Socra AI's motion in code with Claude Code, then stopped letting one still Figma frame stand in for anything that moves

Jumi Jeong found that she and Claude misread motion from single Figma frames five times, so she now judges motion by playing it in Storybook.

Done withClaude CodeFigmaStorybook

In-house work on her employer's product (Socra AI). Post drafted with Claude, she says.


WHAT THEY DID

Jumi Jeong, project design lead at Socra AI in Seoul, built the motion for the Socra AI app's screens in code with Claude Code from late August through September 2026. Most motion lived in Storybook, while Figma held one still frame of it.

STEP BY STEP

  1. Motion built in code first with Claude Code and reviewed in Storybook; Figma kept one still frame.
  2. After five misreadings, split sources of truth: Figma for still specs, Storybook for motion.
  3. Handoff now pairs a mid-motion Figma frame with a playable prototype and a Storybook link.
  4. Timing and easing chosen by playing options side by side, slowed down.
  5. Interaction designer's motion rules moved into the design system code with Claude Code, then QA'd.

HOW IT WENT

She says a single still screen led to a misreading of the motion five times, mostly by the AI and once by her. She now treats Storybook as the source of truth for motion and Figma for things that stay still, and hands developers both links.

Reported results: Five misreadings before the 22 Sep standard; one more caught the same day on 30 Sep; rules moved into 41 places in a day; two motion defects found only by playing the screen.

WORTH KNOWING

A dated, first-person account of a failure mode many designers will meet when an agent reads their Figma files: a frozen frame looks like a finished state. Her three checks are simple to copy.

TRY IT

  • Before you or an agent edit a frame, check whether it is one moment of something that moves (frame variants, prototype links).
  • If motion must be shown as a still, draw two or more frames side by side, such as 0 s, 2.4 s and 4.8 s.
  • Choose timing by playing options side by side, slowed down; put a link to the playable version next to the still.
Read the original ↗

Rates the entry, not the tool.

Source: Jumi Jeong · Medium (personal)Open as a page

  • Work done: Aug 2026 – Sep 2026 (She writes that the examples in the post are from August to September 2026; she built the motion from late August through September.)
  • Source published: Nov 22, 2026
  • On 4TC: added Nov 22, 2026 · checked Nov 22, 2026
About this source

Type: First-person workflow · Firsthand report

  1. Work Log 11: Should you use Figma to show motion and interaction to AI?
    Jumi Jeong · Medium (personal) · Published Nov 22, 2026 (Posted 22 Nov 2026; English version of her Korean original (Brunch, Nov 2026).) · Checked Nov 22, 2026
    Primary: the designer's own first-person work log about her in-house product work. No sponsorship, affiliate or vendor tie stated; no promotional links.
    Access: The author notes the story was written with an AI writing program's help and translated from Korean with Claude.
  2. About Jumi Jeong
    Jumi Jeong · Medium (profile) · Publication date not stated (Profile page; undated.) · Checked Nov 22, 2026
    Author identity and role (self-description).
    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

  • From late August through September 2026 she built the motion for Socra AI's screens in code with Claude Code; most of it was made first in Storybook, and Figma held one moment of it as a single still screen. (reported) [1]
  • She says that one still screen led to a misreading of the motion five times; mostly the AI took the screen as the finished state, and once she trusted that call and almost changed the Figma file. (reported) [1]
  • The AI read a brand-banner logo as a still symbol and planned to nudge it by 2 to 3px; it was a 48-frame moving component whose centre of gravity changed every frame. (reported) [1]
  • The AI judged a hand-drawn mid-motion frame of graph bars (2px gaps against 3px in the component) to be wrong and proposed swapping in the component; she approved it, but the AI's recheck before the change showed the frame was one moment of the bubbles being absorbed. (reported) [1]
  • A border colour that travels around a toggle, drawn by the AI as one frozen frame, looked like a 'still border' option the team had already dropped; the Figma guide now shows it at 0, 2.4 and 4.8 seconds. (reported) [1]
  • To choose how bubbles are absorbed into bars she made three options, switched to a two-choice screen, lined them up on one Storybook screen and played them four times slower. (reported) [1]
  • She kept the 135ms bubble interval already in the code instead of the 80ms written in Figma, which had been tuned for three or four photos and made ten AIs' landings overlap. (reported) [1]
  • After the build and tests passed, Claude opened the Storybook screen and measured positions, finding two defects: full bars reset to zero when the card width changed, and bubbles slid toward the middle of the screen. (reported) [1]
  • Working from an interaction designer's numbered motion rules (durations of 120, 160, 200, 320 and 480ms), Claude moved the rules into 41 places across the code in a single day; the values went through that designer's QA before merging into the design system repo. (reported) [1]
  • She set the standard 'don't judge a moving design from one still screen' on 22 September, and caught a repeat on 30 September the same day. (reported) [1]

4TC interpretation

Our reading, not something the source says.

Agents reading Figma treat what they see as final. Her fixes are about the file, not the prompt: flag what moves, draw two or more frames, and pick timing by playing options side by side.

Designer impact

Alleged [1]

An agent reading a design file treats a single still frame as the finished state and proposes 'fixes' that would break the motion.

  • Mark what moves in the file and link the playable version next to the still.
  • Ask the agent to recheck intent before applying a change to a frame.

Alleged [1]

Passing builds and tests do not show how motion looks on screen.

  • Play the motion and review it by eye before sign-off.

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.