You're in charge of the design. the tool's in charge of the execution.

said that in a tutorial i recorded for contra university and it's the most honest thing i know about where this work is going.

took a figma design, dropped it on the canvas, spun three variants off one client note, published a live clickable site. what used to be four or five revision rounds took about five minutes.

so when execution gets that cheap, it stops being the thing you sell. a client can get a polished working page out of one sentence now. what they still can't get is the call under it. who it's for. what it says. what it refuses to say.

I'm not nervous about teaching designers to move this fast, the faster everyone executes the more obvious it gets who can actually decide.

https://www.youtube.com/watch?v=eVnd65hm_ks

woooo it's live!

Did you know a tornado formed the year you were born? Not a real one. A data one. Type your birth year. Watch the storm react - the speed, the color, the rage of it - all driven by the exact CO₂ levels recorded that year. 🌪️Live Site - https://thedatatornado.figma.site

🎨Figma Make - https://www.figma.com/make/onDJsdMQ3PQV2B8xkSzHKn/TheDataTornado

📋FigJam Board - https://www.figma.com/board/2P5FGzsc6faOl2a2JK2GDo/TheDataTornado

💻GitHub Repo - https://github.com/isumenuka/Thedatatornado

🔬 The Problem Climate change is the most documented crisis in human history. Scientists have been collecting data for over 65 years. But most people feel nothing when they see the numbers - because a wall of data doesn't make you care. That is a design problem. The Data Tornado is my answer. ⚙️ How It Was Built I started in FigJam - mapping the full app structure, severity color system (Stable → Elevated → Critical → Extreme), and the 65-year climate timeline before touching any build tool. In Figma Make, I loaded my complete design guidelines first - colors, fonts, spacing rules - so every generated output matched my vision from the first prompt. That one step eliminated hours of corrections. The MCP connector was the most critical technical piece: a custom live pipeline to NOAA's servers, pulling real CO₂ and temperature readings automatically every time someone opens the app. No downloading. No pasting. Always live. The hero background video was generated entirely in Figma Weave - I set a start frame and end frame, and Weave generated the full atmospheric storm footage between them. The Figma Agent handled precision edits throughout -clicking directly on individual elements, repositioning buttons, aligning sections, without touching anything else. Supabase powers the share cards, news gallery, and live data caching. GitHub handles deployment. 🛠️ Tools Used

→ FigJam: full app structure, severity system & data flow diagrams

→ Figma Make: prompt-to-code app with custom NOAA MCP connector

→ Figma MCP: live pipeline direct to NOAA's climate API

→ Figma Weave: AI video generation for the hero storm background

→ Figma Agent: precision element-level UI edits throughout the build

→ Supabase: backend for share cards, news & data caching

→ GitHub: deployment and version control ✨ Key Feature - Birth Year Telemetry Enter your birth year. The app instantly generates your personal climate log -the exact CO₂ concentration the year you arrived in the world, your temperature anomaly then vs. now, your severity level at birth vs. today. It stops being a global statistic. It becomes yours. Most people go quiet when they see their own number.

What happened on the day you were born? Share your link in the comments! THIS IS MINE - https://thedatatornado.figma.site/?share=d9844bb7-12d7-4c5a-94e8-ebd84ade9f8b