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

I joined the Config Makeathon and built BriefOS — a client brief operating system for designers, studios, and freelancers.

The problem I wanted to solve is something almost every designer deals with:

Client projects rarely start clean.

They usually start with scattered notes, vague goals, random references, unclear positioning, mixed opinions, and no approved direction. That chaos creates slow starts, endless revisions, weak strategy, and confusion between the designer and the client.

So I built BriefOS to turn that mess into a clear, structured website blueprint.

The idea:

Client chaos → AI signal extraction → website blueprint → visual direction → wireframe → client approval

Inside BriefOS, a designer can collect messy client input, organize it into useful categories, extract important signals, build a sitemap, generate copy directions, choose visual routes, adjust wireframes, and send decisions into a client approval room.

I wanted the product to feel less like a generic AI tool and more like a real project command center.

What I built:

Command Center to track the full project workflow

Intake Wall for messy client notes, links, screenshots, and references

Signal Extractor to identify offer, audience, CTA, tone, gaps, and contradictions

Blueprint Builder for sitemap, homepage structure, copy, and conversion path

Visual Lab for mood, palette, typography, layout direction, and style routes

Wireframe Studio for reviewing and refining the homepage structure

Approval Room for client decisions, comments, approvals, and revision requests

I also focused on making the experience interactive instead of just “AI magically does everything.”

The user can tag notes, approve or reject signals, choose direction, reorder sections, compare options, adjust wireframes, and approve final decisions.

Built using Figma Make as part of the Config Makeathon.

The goal was simple:

Help designers move from confusion to clarity faster — while keeping strategy, copy, design, and client approval connected in one workflow.

Still more I’d love to improve:

deeper real data inputs

stronger drag-and-drop behavior

better client presentation mode

more polished animations

live export options

more visual direction templates

But for this version, I’m happy with the core concept: a useful AI workflow product built around a real design problem. preview link:https://www.figma.com/make/LhthPqSGpwgLBKVoJdQLHG/Begin-Project?fullscreen=1&t=aPQZNZHYQiD53qn0-1&code-node-id=0-9

#ConfigMakeathon @figma #FigmaMake #ProductDesign #UIDesign #AIDesign #WebDesign #DesignTools #Contra

This is actually a really useful idea. Turning messy client briefs into a clear workflow solves a real problem.