How Grok Bot designers use AI agents to build personal sites and product prototypes | John Bai & Peng Zheng
- ID
- 24189
- Status
- summarized
- Published
- 14 Sep 2026, 8:04 PM
- Fetched
- 14 Sep 2026, 9:15 PM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/how-grok-bot-designers-use-ai-agents
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 7.5
- Created
- 14 Sep 2026, 9:15 PM
- Tags
- Audience
- vibe_codersai_agent_usersdeveloperssaas_founders
What happened
Two Grok Bot team designers at SpaceXAI share concrete AI agent workflows: Peng built a self-updating personal website using Grok Bot as the entire backend pipeline (no CMS, no Figma file) that updates from a photo or place name via Google Places API, while John uses a Figma Bro bot connected via MCP to handle production design tasks remotely, including voice-memo-directed Figma work from his phone. They also describe a DevBot workflow for turning 'shower thoughts' into working prototypes without routing through a PM or engineer, and a 'trash can method' of software development.
Why it matters
If you build with AI agents, the specific patterns here are immediately copyable: MCP-connected Figma automation, photo-to-portfolio-update pipelines, and voice-to-prototype loops that collapse the gap between idea and working artifact. Try wiring an MCP server into a tool you already use daily (Figma, Notion) and test whether a single bot can own an entire pipeline end-to-end, as Peng did with his site.
Discussion angle
Which of your current multi-step workflows (design handoff, content updates, prototyping) could be replaced by a single agent pipeline, and what breaks first when you try?