Vibe Code in Figma Make with Miggi from Figgi

Michael: Hey.

Sean: Hey, hey.

[Music]

Michael: Look at that.

[Music]

Sean: Hey. Hey, hey. Right.

Michael: All right. Well, welcome, welcome, welcome. We're excited to have you here for our third episode of Build, Launch, and Earn. First and foremost, tell us where you're viewing from – put it in the comments or the chat. We'd love to see where everybody's coming in from. If you're coming back, let us know this is a repeat visit and what you enjoyed most.

To get us started, I'm Michael. I'm a product manager, previously UX and full-stack software engineering. I'm excited to be here with my co-host, Sean.

Sean: Hey everyone! So happy to have you here. I'm excited to be in the studio with Michael today. This is our fourth stream together – we've been doing these monthly and it's amazing to see familiar faces in the chat. Definitely, if you’re just popping in, let us know you’re here and where you're viewing from.

I’m Sean Pritskow – a marketing strategist, a designer, and co-host of Build, Launch, and Earn alongside Michael. We’re so stoked to have you.

If you’re new, Build, Launch, and Earn is about equipping web designers with tools to build, launch, and earn – live, and in community. Especially if you’re freelancing or working remotely, it can feel isolating. That’s why we do this live – so we can connect and support each other.

Michael: Today in the studio, we’ve got Miggi from Figgi. Miggi is a designer advocate at Figma. He bridges education and industry – partnering with educators to bring collaborative design into classrooms while leading cross-functional efforts in brand, product marketing, and creative storytelling. He also teaches UX/UI and digital design at RIT in Rochester.

Miggi: Yeah, thanks for having me.

Michael: So excited to talk Figma and specifically, Figma Make. Quick setup for today’s stream: we’ll explore what’s possible with Figma Make – from prompting and prototyping to actually publishing and testing your ideas. You can even hook up payments and monetize.

Stick around until the end – we’ve got a giveaway. Three people will win a book of their choice from Stripe Press and some surprise Figma goodies. Fill out the quick survey at the end to enter.

All right, Miggi – welcome to the stream.

Miggi: Thanks, Sean! Really fun to be here. So – Figma Make. For folks who’ve never heard of it, it’s part of Figma’s suite of tools that lets you go from prompt to publish. In theory, you can go from prompt to product. But really, we think of it as a prototyping tool. It’s a utility to build utilities.

My own explorations started with education. I work with educators and students and think a lot about what this tool means for them. It’s a way to test ideas and iterate quickly. Everyone from designers to HCI students to developers can use it. It’s just another tool in the arsenal – but it offers more than traditional static prototypes.

Instead of just click-through frames, with Make, you can add logic and AI to your design context to create interactive prototypes. I can walk you through what that interface looks like and show some examples.

Sean: Amazing. I feel like this is everywhere right now – on Twitter, in product convos – and people are excited, but also skeptical. I haven’t explored it much myself yet. I think a lot of us throw in a first prompt, see a wow moment, and then stall when it comes to integrating it into real workflows.

So I’m excited to dig in with you.

Miggi: Cool – if you’re looking at my screen, you’ll see Figma Design – our flagship tool. This is where people collaborate on product design. From there, you can jump into Figma Make to create prompts that generate working utilities and prototypes.

When you start a new Make file, you can:

• Prompt from scratch
• Start with a frame from Figma Design
• Explore community-made examples

You can paste in a design and describe what you want to build. For example, here’s a radial navigation pattern – something you’d normally prototype with transitions. But if you wanted the elements to stagger out independently, you’d need logic. That’s where Make comes in.

Another example: I wanted to visualize a color picker using OKLCH, which isn’t natively supported in Figma. I prompted Make to build it. Then I layered in requests for color suggestions, palette generation using color theory, and custom harmonies. All of that was done incrementally through prompting.

Eventually, I had a tool that let me tweak values and output SVG code – which I could copy back into Figma as a graphic. That’s what I mean by building utilities for yourself.

Sean: So cool. It really becomes a tool to test and expand your ideas as you go.

Miggi: Totally. I’ve also built clocks, 3D visualizers, and even a functional DJ mixer. That one was for a drone light show in San Francisco. I needed a way to perform the music I’d composed. So I made a Make file where I could upload tracks, visualize the mix, and use keyboard shortcuts to fade and control the decks. All built with prompts.

Sean: That’s wild. Should we build something together?

Miggi: Yeah! Let’s make a basic Asteroids-style game. I’ll start by drawing a little spaceship in Figma Design. Then I’ll prompt: “Create an Asteroids-style game using this design. The hero ship should move left and right with arrow keys. Return key to shoot missiles.”

Sean: This prompt is just plain language. That’s super approachable.

Miggi: Exactly. People get nervous about prompt syntax. But natural language often works just fine. And you get better at it as you experiment.

So here we go – it’s generating the game. I’ll add more to the prompt: “Add a scoreboard. Five levels. Five lives. Enemies shoot downward.”

Boom – game’s up! It’s live. I’m shooting, completing levels. It’s even suggesting improvements like adding sound, power-ups, and particle effects.

Sean: It’s responsive too! Wow.

Miggi: Yep. You can switch to mobile preview. And I can even go in and edit the code or make style tweaks. You can spot-edit visuals, padding, fonts – all inline. It’s not a black box.

You can even hit “Copy Design” to bring your Make output back into Figma as editable layers. The fidelity is high – named layers, variants – it’s real design data.

Michael (via chat): We’ve got a question from Aaron – what if you want to save user data, like score history? Would you need a backend?

Miggi: Great question. You can use Supabase for that. You’d prompt: “Add score tracking and save it to Supabase.” Supabase is like a plug-and-play database. It’ll prompt you to link your account and manage the logic.

We even have examples of this integrated with Stripe. A friend built a store with Stripe test accounts connected through Supabase – all prompted in Make.

Sean: Another question – do you know which AI model Make is using?

Miggi: Not off the top of my head. Models are updated frequently and different tools in the Figma suite let you customize them. I’d rather not misspeak since things are changing rapidly.

Michael: What about using Make in a design team’s real workflow? Where does it fit?

Miggi: Great question. I see Make as useful in three big ways:

1. Prototyping ideas faster and with higher fidelity
2. Building internal tools or utilities – like that color picker or music sequencer
3. Communicating vision – a PM could build a quick proof of concept to show intent

Make helps uncover blind spots earlier. You get feedback faster. You can even spot things like empty states, loading states, and user feedback mechanisms you might miss with static mockups.

You can use your team’s existing design libraries too. Just link them in and Make will apply your styles. You can also set design guidelines like “avoid absolute positioning” and Make will follow them while generating.

Sean: So much potential here. I’m super excited to dive deeper.

Michael: Last thing – if you’re watching live, check your email. You should’ve received a quick feedback survey. It’s just a few clicks, and it enters you in our giveaway for a Stripe Press book and Figma swag.

Sean: Also – mark your calendar. Our next stream is Friday, November 21. Michael just dropped the link in chat. We’d love to see you again. Let us know if this time slot works well or if evenings are better.

Michael: Miggi, thanks again for being here.

Miggi: Thanks for having me – this was awesome!

Sean: Bye for now – fill out that survey and we’ll see you next month!