Figma Bro Bot

John Bai has been using Grok Bot to design Grok Bot. It has not replaced Figma or the rest of his kit. It changed how many ideas he is willing to explore, because the agents keep working while he is AFK and because an idea can become a thing he can actually try before it has to be sensible, feasible, or on the roadmap. Roster: Figma Bro handles repetitive production work in Figma. Motion God prototypes as he describes how interactions should feel. Experiments is where he sends ideas he wants tangible before he knows what they should become. Devbot answers engineering questions and helps the others understand how an idea should actually get built. They huddle, delegate, and bring work back together. The names make the seats obvious. Experiments got the first brief: make Bots accessible anytime, anywhere — keyboard shortcuts, OS-level entry points, ambient access. It built three. One tucked Bot into the Mac notch, a home that did not ask him to keep another window open. One had Bot peek in from the desktop corner on hover, more character than chrome. One had Bot follow the cursor as a companion. Experiments delegated character movement to Motion God and desktop behavior to Devbot, then brought the three back as prototypes he could encounter during the day and notice when they felt helpful, distracting, or in between. None of them shipped as explored. That was the point. He had an idea, made three versions real, and learned from each one. Motion God is how he stayed in the motion loop instead of handing keyframes to an expert and waiting. For a promo of the Grok Bot character — Bot appears, notices the app window, bounces into place — he did not want a screenshot recreation. He had Motion God build a localhost playground around the actual animation spec file so he could tune timing, springs, distance, scale, and easing on the production asset, then give comparative notes like "hold the look down-left longer" and "bounce is too exaggerated" and watch the whole sequence again. Figma Bro is the repetition seat. For onboarding they wanted starter Bots (Chief of Staff, Inbox Triage, and eighteen more) with differentiated portraits. He built one auto-layout component and asked Figma Bro to populate the rest. Same pattern for the tools newcomers actually use: he made the page template, Figma Bro searched for the correct assets and placed them by usage likelihood. He does not want Figma Bro eyeballing any of this. Through the Figma MCP it inspects the file and uses exact x and y, width, height, spacing, typography, fills, strokes, and component structure. An existing frame is the source of truth. Wrong logo variant, outdated component, tenth card spaced differently from the first — that is the class of miss this seat exists to prevent. Judgment stays his. Grok Bot does not replace it. It gives him more versions to use it on. He does not publish, ship, or replace production assets until he says so. Official guide on x.ai, Aug 24, 2026.