Recipes / Claude Code use cases
Claude CodeWorkflowDev & code

Claude Code app UIs that look and move like a designer's

Breeje Anadkat says the app UIs he builds with Claude Code that look and move well took several rounds of prompting, not one. He starts by telling Claude what the app does and sharing UI and motion references. For some screens he designs in Figma first and puts it next to the build to list exactly what must change. He tests by tapping through the app, because a transition can look great in a clip and still feel slow.

From Breeje Anadkat on X · Nov 2026

Setup timeNot stated. He says most screens took several rounds of prompting
CostNot stated in the thread. Your Claude Code plan, plus Figma if you mock up screens or states
RunsWhen you're building an app's screens and want them to look and move like a designer made them
NeedsClaude Code, A short description of what the app does, UI references from Mobbin or Pinterest, A motion reference, a clip of the animation you want, Figma, for screens you design first and for the side-by-side check; 2 or 3 states for complex animations, The running build, so you can tap through it, You, approving each round
Last updated2026-11-14

What the source did

  • Most of his app UIs took several rounds of prompting. Expecting one shot means stopping at the rough draft.
  • He starts by telling Claude what the app does and sharing a few UI and motion references, then builds from there.
  • UI references come from Mobbin and Pinterest.
  • Some screens are quicker to get right if he designs them in Figma first. He then puts the Figma design next to Claude's build and points out exactly what needs to change.
  • He usually sends Claude a motion reference. About 5 to 10% of the time, when he can't find the right clip or the animation is complex, he mocks up 2 or 3 states in Figma and explains all the states and how they work. His example is a slide with 3 states.
  • He tests the app by tapping through it. A transition can look great in a clip and still feel slow when tapped. He still nudges titles by 2px.
  • The thread closes with an offer of design and MVP build services for founders, which we've left out.
“People keep asking how I get Claude Code to make app UIs that look and move like this.”— Breeje Anadkat (@BreejeAnadkat), X

Summary written by Agent Cookbook from the original post. See the original for the full context. How we source recipes

Our notes

What it takes
Claude Code, a short description of the app, UI references from Mobbin or Pinterest, a motion clip (or 2 or 3 Figma states for a complex animation), and a build you can tap through. He published no prompt; the brief is ours.
Where it breaks
Expecting the first draft to be finished: most of his screens took several rounds. Judging motion from a clip alone, when a transition can look great and still feel slow when tapped.
Human checkpoint
Nothing ships to an app store or to users without you. You approve each round and decide when a build is good enough. Sending, buying, posting and deleting always need a human.
Tools involved
Claude Code, A short description of what the app does, UI references from Mobbin or Pinterest, A motion reference, a clip of the animation you want, Figma, for screens you design first and for the side-by-side check; 2 or 3 states for complex animations, The running build, so you can tap through it, You, approving each round

✓ Verified Source link checked and still live. Notes by Thomas, editor. How we verify

Copy the prompt

Ours Our version, based on Breeje Anadkat's thread. He didn't publish a prompt, repo or skill, so this brief is ours. Fill in the [BRACKETS].

APP BRIEF FOR CLAUDE CODE (our version, based on Breeje Anadkat's thread) What the app does: [two or three sentences: who uses it, the main job, and the screens] Round 1: build the core flow. UI references for layout and style, one per screen: [Mobbin or Pinterest links] Motion reference for the main transitions: [a clip or link] Expect several rounds. Don't stop at the rough draft. For any screen I designed in Figma: compare your build with the Figma design side by side. List exactly what needs to change, then change only that. If there is no clip for an animation, or it's complex: wait for my Figma states (2 or 3) and build from those, with the states and how they change. Each round: tell me what you changed, so I can tap through the build and check how the transitions feel.

Approval rule

🛡
Nothing ships to an app store or to users without you. You approve each round of changes and decide when a build is good enough. Sending, buying, posting and deleting always need a human.

Set it up

  1. Tell Claude Code what the app does, and share a few UI and motion references from Mobbin or Pinterest.
  2. Build the first version, and expect several rounds of prompting.
  3. For screens that are quicker in Figma, design them first, put the Figma design next to Claude's build, and list exactly what must change.
  4. Send a motion reference for each main animation. If there's no clip or the animation is complex, mock up 2 or 3 states in Figma and explain how they change.
  5. Tap through the build yourself. Check that transitions feel right, not just that they look right in a clip, and nudge small things like title position.

Common failures

⚠
  • Expecting the first draft to be the finished screen. Most of his took several rounds.
  • Judging motion from a clip alone. Tap through it: a transition can look great and still feel slow.
  • Leaving out the motion reference. He usually sends one, and mocks up states in Figma when no clip exists.

Variations

  • For simple screens, skip the Figma mock. He only mocks up states when there's no clip or the animation is complex.

Related setups: The Claude Code team's habits: parallel worktrees, plan first, skills → · Research, annotated plan, then implement → · Run Claude Code by voice with a chief agent →

Get the 10 best agent setups. Free.

Plus new recipes every week. One email, no spam.

Unsubscribe anytime. Privacy

Related recipes

Same job: Dev & code

More Claude Code recipes

In these guides: More Claude Code use cases →

Read original ↗