Prototype a promo video and design work with bots
How a designer uses always-on Grok Bot agents to explore more ideas, work with real production assets, and keep judgment in the loop. Task: How a designer uses always-on Grok Bot agents to explore more ideas, work with real production assets, and keep judgment in the loop. At SpaceXSI, we’re building agents that can take an idea and begin making it real. For designers, that changes what’s worth exploring. Design has always been a process of giving form to an idea: making something, reacting to it, and changing it until it begins to feel right. As making becomes easier, we can explore more directions, react sooner, and let an idea reveal what it wants to become instead of defining it before we begin. I’ve been using Grok Bot to design Grok Bot. And while this hasn’t replaced existing tools in my kit, using AI design agents has changed both how quickly I can bring an idea to life and how many ideas I’m willing to explore in the first place. Grok Bot gives me a team of always-on AI design agents with their own computers. They have memory, can use tools, and can carry work from an initial idea to a finished artifact. They also keep working while I’m AFK, which matters because inspiration often strikes away from my desk. Meet my bots Figma Bro handles repetitive production work in Figma. Motion God helps me prototype as I describe how interactions should feel. Experiments is where I send ideas that I want to make tangible before I know exactly what they should become. Devbot answers engineering questions and helps the other bots understand how an idea should actually get built. The names make each bot’s role clear, but they don’t work in isolation. My design agents can huddle with one another, delegate parts of a project, and bring the work back together. Here are three recent examples. Experiments: you can just do things One of the earliest ideas I wanted to explore was how to make Bots accessible anytime, anywhere. I wanted to try keyboard shortcuts, OS-level entry points, and other ways of invoking one, so I tasked Experiments with building a series of explorations in ambient Bot access. The first placed Bot in the Mac’s notch. It could remain tucked into a fixed location while it worked, emerge when something needed attention, and expand into a small workspace when I wanted to see more. It gave the agent a home without asking me to keep another window open. Bot tucked into the Mac notch. The second had Bot peek in from the corner of the desktop on hover. This felt less like a persistent interface and more like a character entering the scene when invoked or when it had something to say. Bot peeking in from the corner of the desktop. The third had Bot follow the cursor as a companion, creating a closer connection to whatever I was doing in the moment. Bot following the cursor as a companion. I described the behaviors to Experiments, and it worked out how to make each one tangible. It delegated the character movement and transitions to Motion God, the desktop behavior and implementation questions to Devbot, then brought everything together into prototypes I could actually try. I could encounter each version naturally throughout my day and notice when it felt helpful, distracting, or somewhere in between. That’s why I keep an agent specifically for Experiments. I don’t need to decide that an idea is sensible, feasible, or destined for the roadmap before making it real enough to judge. None of these concepts shipped exactly as explored. That wasn’t really the point. I had an idea, made three versions real, and learned from each one. You can just do things. Motion God: work with the real thing Historically, motion is where I’d hand an idea off to an expert on the team. I could describe the behavior or mock up a few keyframes, but someone else would have to make it real before I could react to it. With Motion God, I can stay in the exploratory loop and direct the interaction by feel. As part of an email campaign, I wanted to prototype a promotional video of the Grok Bot character. The sequence was fairly specific: Bot appears, notices the app window, and bounces into place. I didn’t want the design agent to recreate the character from a screenshot or generate an approximation. I wanted it working with the same asset that already lived and moved in the product. So I had Motion God build a playground on localhost around the actual animation spec file. That way, I could manually adjust timing, springs, distance, scale, and easing while it was running.; tools: Grok Bot. Human role: The original post does not say how a person stayed involved.; limitations: The source does not state specific technical limitations, costs, or integration hurdles. It notes that AI design agents have not replaced existing tools in the designer's kit. The workflow relies on the agents' ability to access real production assets and maintain memory, which may require specific setup or permissions not detailed in the text..
Tools
Published on Agent Work Atlas:
Overview
How a designer uses always-on Grok Bot agents to explore more ideas, work with real production assets, and keep judgment in the loop.
Workflow
How a designer uses always-on Grok Bot agents to explore more ideas, work with real production assets, and keep judgment in the loop. At SpaceXSI, we’re building agents that can take an idea and begin making it real. For designers, that changes what’s worth exploring. Design has always been a process of giving form to an idea: making something, reacting to it, and changing it until it begins to feel right. As making becomes easier, we can explore more directions, react sooner, and let an idea reveal what it wants to become instead of defining it before we begin. I’ve been using Grok Bot to design Grok Bot. And while this hasn’t replaced existing tools in my kit, using AI design agents has changed both how quickly I can bring an idea to life and how many ideas I’m willing to explore in the first place. Grok Bot gives me a team of always-on AI design agents with their own computers. They have memory, can use tools, and can carry work from an initial idea to a finished artifact. They also keep working while I’m AFK, which matters because inspiration often strikes away from my desk. Meet my bots Figma Bro handles repetitive production work in Figma. Motion God helps me prototype as I describe how interactions should feel. Experiments is where I send ideas that I want to make tangible before I know exactly what they should become. Devbot answers engineering questions and helps the other bots understand how an idea should actually get built. The names make each bot’s role clear, but they don’t work in isolation. My design agents can huddle with one another, delegate parts of a project, and bring the work back together. Here are three recent examples. Experiments: you can just do things One of the earliest ideas I wanted to explore was how to make Bots accessible anytime, anywhere. I wanted to try keyboard shortcuts, OS-level entry points, and other ways of invoking one, so I tasked Experiments with building a series of explorations in ambient Bot access. The first placed Bot in the Mac’s notch. It could remain tucked into a fixed location while it worked, emerge when something needed attention, and expand into a small workspace when I wanted to see more. It gave the agent a home without asking me to keep another window open. Bot tucked into the Mac notch. The second had Bot peek in from the corner of the desktop on hover. This felt less like a persistent interface and more like a character entering the scene when invoked or when it had something to say. Bot peeking in from the corner of the desktop. The third had Bot follow the cursor as a companion, creating a closer connection to whatever I was doing in the moment. Bot following the cursor as a companion. I described the behaviors to Experiments, and it worked out how to make each one tangible. It delegated the character movement and transitions to Motion God, the desktop behavior and implementation questions to Devbot, then brought everything together into prototypes I could actually try. I could encounter each version naturally throughout my day and notice when it felt helpful, distracting, or somewhere in between. That’s why I keep an agent specifically for Experiments. I don’t need to decide that an idea is sensible, feasible, or destined for the roadmap before making it real enough to judge. None of these concepts shipped exactly as explored. That wasn’t really the point. I had an idea, made three versions real, and learned from each one. You can just do things. Motion God: work with the real thing Historically, motion is where I’d hand an idea off to an expert on the team. I could describe the behavior or mock up a few keyframes, but someone else would have to make it real before I could react to it. With Motion God, I can stay in the exploratory loop and direct the interaction by feel. As part of an email campaign, I wanted to prototype a promotional video of the Grok Bot character. The sequence was fairly specific: Bot appears, notices the app window, and bounces into place. I didn’t want the design agent to recreate the character from a screenshot or generate an approximation. I wanted it working with the same asset that already lived and moved in the product. So I had Motion God build a playground on localhost around the actual animation spec file. That way, I could manually adjust timing, springs, distance, scale, and easing while it was running.
Reported result
The source does not report measured business outcomes or metrics. It states that the workflow allowed the designer to explore more ideas, react sooner, and work with real production assets rather than approximations. Specific examples include three ambient bot concepts that did not ship exactly as explored but provided learning, and a motion prototype where the designer could tune timing and easing directly.
Human role
The original post does not say how a person stayed involved.
Limitations
The source does not state specific technical limitations, costs, or integration hurdles. It notes that AI design agents have not replaced existing tools in the designer's kit. The workflow relies on the agents' ability to access real production assets and maintain memory, which may require specific setup or permissions not detailed in the text.
Try it
Act as a design lead using Grok Bot agents. I want to prototype a new interaction pattern for [Product Name] using real production assets. First, set up a 'Motion God' agent to build a local playground around the actual animation spec file for [Specific Component]. I will provide feedback on timing and easing; you must adjust the prototype immediately. Second, use 'Figma Bro' to populate [Number] cards in Figma using an existing auto-layout component, ensuring exact spacing and typography. Third, have 'Experiments' agent generate three distinct concepts for [Feature Idea] and delegate implementation details to 'Devbot'. Before finalizing any output, show me the prototype for review. Do not ship any changes without my explicit approval. If assets are missing, ask for the specific file paths.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.