Andres GonzalezFlowglad · Designer by day, Batman by night

Claude, make a System Architecture Diagram of the universe

20 May 2026 · 1 min

Watch on YouTube

0:58

In this monologue, the speaker, a designer, pushes back against the hype of AI influencers urging designers to learn Claude Code, arguing that technical design ability is a multiplier that lets technical designers consistently outperform non‑technical ones. The speaker outlines a practical workflow for leveraging Claude Code together with the collaborative whiteboard tool Miro to create system‑architecture diagrams that aid both design understanding and engineering collaboration. The process involves: (1) connecting Miro to Claude Code via an MCP server; (2) prompting Claude Code to analyze the architecture of a specific feature before any UI changes; (3) instructing Claude to generate a diagram that includes a glossary of terms; and (4) sharing the resulting document in Miro so engineers can answer the designer’s questions. The speaker emphasizes that these diagrams become shared intelligence because Miro is where the engineering team’s thinking lives, turning the visual artifact into a collaborative knowledge base.

Chapters

Cuz I'm sick of all the AI influencers telling designers that they need to learn Claude Code. And no one's really talking about how Claude acts as a multiplier and a technical designer will always outperform a non-technical designer at producing quality software. And designers like myself already know that design isn't just about how something looks, it's about how something works. Don't call me Steve Jobs though. So here's how I'm using Claude Code with Miro to generate a system architecture diagram to learn how a system works, collaborate with my engineering team while also making things look pretty. First thing that I'm gonna do is I'm gonna connect Miro to Claude Code using their MCP server. Next, I'm gonna prompt Claude Code to to carefully analyze a system architecture of a particular feature that I need to understand before making any sort of UI change. Then I'm gonna tell Claude to generate a diagram using the MCP server with a glossary of every term at the bottom. And finally, I'm gonna share this doc, collaborate with my engineers so they can answer the rest of my stupid questions. And trust me, I have a lot of them. And these diagrams become shared intelligence because Miro is a collaborative platform where most of my engineering team's thinking actually lives, which is phenomenal because