# Design-to-Code Workshop with Claude Code, Cursor & Figma (Friends of Figma Miami - Feb 2026)

Channel: The Design Project
Video: https://www.youtube.com/watch?v=SEy1WPjPF3k
Duration: 43 min
Language: English
Words: 6439
Transcript page: https://viewrankai.com/tools/youtube-transcript/SEy1WPjPF3k

---

[0:00] Hey guys, how's everyone? Good. Okay. Um, so today I'm going to be showing you guys a design to code workshop. Um, so I'm sure you guys are familiar with AI like Jonathan said. Um, maybe I'll do a little intro first. So my name is Diane. I am the CEO and co-founder of The Design Project. The Design Project is one of the first subscriptionbased design agencies. We work with startups that have been funded. Um some of our startups have

[0:30] been acquired by Nvidia, Slack, Mr. Beast and we are basically going in and we are working with product teams and we are implementing AI into our processes today. Um one of the biggest things that I have seen that has changed the game is me being able to actually take my designs and front-end code. So I can now hand off front-end code to my product teams which is really a game changer. It speeds everything up. That's what I'm

[0:59] going to show you guys today. So, first of all, I want to understand the people in the room. How many of you are students here today? Nice. Okay. How many of you are product designers working in the space now? Nice. Okay. Okay. How many of you guys are already using AI in some of your processes? Perfect. Okay. And how many of you are pushing code? How many of you are actually

[1:27] Nice? That's awesome. Okay, great. That's great to hear. Um, okay. So, for all of us, does this sound familiar? Um, it's kind of the old way, right? We used to spend time with PRDs and we would get PRDs as designers. We would maybe go to wireframes, we would do inspo, we would do V1, V2, V3, and Figma. Um, and then eventually once we get approval, we would take our Figma, we would annotate this to annotate it and then hand it off to devs and then devs would go and build it and then we would have to go and review it and then we would iterate on

[2:00] it and eventually we would get to the final version. Um, that's that's the old way that way I personally think is going to be the past very soon. Um, what you're going to learn today is understanding the new design to code workflow, learning tools, building a real product. We're actually going to build a real product today. Um, and leave with everything you need to actually take it into your company and

[2:25] start shipping code. So, how many of you have been able to set up your environment? Um, do you have GitHub? You have Cursor installed, Claude Code, Figma MCP? Can I get a a show of hands? I'm just curious how many we got. Okay. Okay. No worries. Um, so the ones that have, you guys can actually join me and we can do this together. Um, for those that haven't, that's no worries. You're going to see how I do it and how you can do it. Um, when you set it up and when you get to that level. Um, also I know that this is going to be on YouTube, so you will be

[3:02] able to reference this video when you guys are ready to. Um, sound good. Perfect. Um, okay. I also brought some guests with me. Um, I brought Elena who is head of product at Arrive and she is on the forefront of AI doing many things as a designer with AI. Um, and I also brought Vro here who is a lead AI ML software engineer. So, do we have any

[3:26] other engineers in the room? Oh, there you go. [laughter] Yes, one. Oh, two. Perfect. There we go. Perfect. Um, so to set the stage for those of you that are going to walk along this process with me and for those of you that are just watching, there are a lot of things that happen when you start to code. A lot of things

[3:49] break. There's a lot of troubleshooting. This is definitely going to happen. I'm sure we'll run into some errors that we're going to have to fix together. Um, but if you guys have questions along the way and you feel stuck, you can raise your hand and Elena and Viral will try to help you. again. Maybe they won't be able to because we might need to do more troubleshooting, but I wanted to bring them along because they are experts and if you guys do need some help, they are

[4:14] happy to help you. Okay, what are we going to be working on today? Um, we are going to be redesigning the LLM Council. What is that? What are we doing? Okay, so first this is an open-source project. Basically, open source means anyone can have access to the code. They can edit the code. They can do their own thing. Um, they can post, they can basically take the code and do what they want with it. It's open. Everyone has access. Um, this project is created by Andre

[4:45] Carpathy. Who knows Andre Karpathy? Anyone here? Okay. Andre Karpathy, he basically um came up with the term vibe coding. So, he's like on the forefront of AI. Um, he was a founding member of OpenAI. He used to work with Tesla. Um if you guys don't already, you should follow him on X because he's always on the cutting edge and he's like pushing the boundaries of what AI can do. So it's super exciting. Um for a weekend project, he built this thing called LM Council. LLM council is basically a place where um you can get you can ask a question to AI and all of the AIS will

[5:23] answer and then all of the AIS will grade each other's answer and then there's going to be someone or one there's going to be a council that decides which answer is best. So it's kind of cool. Um, and for us to get started, um, is first we need to access the repo, the open source repo. So I have this bit.ly link here. If you guys go and open this link,

[5:54] you're going to get to this. This is the LLM Council GitHub. We are actually going to take this. We're going to copy it. And now we're going to go into cursor. Cursor is basically a CLI. It's a place where you can um interact with code on your computer. We are going So if you guys don't have this view, you basically

[6:21] go and you say new window. When you go into new window, you're going to go to clone repo and you're going to paste. Okay. So now you need to create a folder where all of your projects are going to live. What we're doing right now is we are taking that GitHub repo and we are putting it on our computer locally so that we can take it and we can manipulate it, play with it, whatever we want to do. And then we're going to push it back to the codebase in GitHub at the end. So I have this folder called coding. That's what I suggest you guys

[6:54] do. I'm in just my computer. I have coding and then this is where I have all my projects. So once you so create a folder called coding and then we're going to select as repatory repository destination and you're going to hit that. You're going to hit open. And now your project is officially on

[7:23] your computer.

[7:34] So for all of you guys that are struggling to clone, oh sorry for all of you guys that are struggling to clone is do you see this chat when you open cursor? You guys have a chat? You can actually paste the GitHub link and say clone this repo. This is how you code with AI. It's constantly there's 10 million ways to do it and there's always going to be an issue. Okay, I'm gonna keep moving for time sake. Um, if you guys keep getting stuck, don't worry. This is this is going to be a lot of information. Um,

[8:19] but we'll we'll keep moving. Um, okay. So, for all of you that have your GitHub repo in cursor, I'm going to show you how to use cloud code. So, Azie brought up. Um, if you do not have a Claude code paid account, you can't use cloud code. Most of you should have set it up before, but if you didn't, you can use the chat, the native AI cursor chat. I prefer cloud code um personally because I think it's just connected to way more um and cloud code's always like on the cutting edge of coming out with with AI but that's my preference. So um whatever you guys want

[9:03] to use um okay so I'm actually gonna change some things around. Let me show you guys. How many of you have cloud code set up in cursor right now? I got stuck. Okay. So, have did you guys do this ahead of time? If not, then Oh, you did. Okay, perfect. So, cursor. Do you see this little um change layout button up here? Okay. If you go to settings, this is weird. I think there's a shortcut, but I have weird shortcuts on my computer, so it's not working. Um, but essentially if you click more

[9:41] actions, do you see cloud code open? You don't see it. Okay. Um, so I think that you guys can go ahead. If you didn't set up the cursor within cloud code, that's totally fine. Um, I'm going to show you how to use cloud code within cursor. There's actually one other way. Let me show you. Sorry. Um, let's go to our terminal. So, if you click here, do you see this terminal right here? You guys have that? Okay. So, if you have if you've set up Claude, you can type in

[10:14] Claude. Enter. And Claude code is going to start running in the terminal. Is that working for some of you guys? Cool. So, when you're in the terminal, just type claude. Okay. So, for you guys who are struggling to get Claude code up in cursor um what the the workound is you're going to click and oh, sorry. You're going to you're going to make sure that this panel shows up. So, it's going to be here. You're going to click here and you're going to go to this little four icons extensions and you're going to

[10:55] click here. Pod code for VS Code. Pod code for Okay, then go with that one. Um, and then install and that should get you up and running. For you guys that have it ready to go, the next step is that we now are going to ask flaad code to read the readme.md file and download dependencies. Read the readme file and download

[11:29] dependencies. So what does this mean? This means that cloud code is going into the readme which is basically defining the codebase and explaining all of the rules. Dependencies are basically external think of like open-source platforms that the the product that you're using relies on. So what it's doing is it's going into the readme and now it is. So the next step is we are we have to put in a secret password so that we are able to use this platform. So for you guys that are working at companies um you're use you're on their repos they most likely will have a passcode for you to be able to access um it's in the form

[12:21] of aenv file. Um, so what you guys need to do is I've actually created av file with $50 credit for all of us to use to be able to actually use LLM Council. Um, so if you guys want to go to this bitly link right here, this is the last one, I promise. Um, we're going to create av file that's

[12:48] storing the secret for us. You're going to copy that code and now you are going to go into cursor and you're going to hit this new file. Do you guys have this set up? If you click here, you will be able to see the the folders. Okay. So, you're going to click this new file and you're going to say

[13:12] NV enter. When you do that, this should pop up. Now you're going to paste.

[13:30] You're going to paste that code. Once you paste that code, you're going to save. Command S. Old school. So now we can close this window if we want. Um, we're going to go back to cloud code. So, the next step, we need to run the servers. What does run the server mean? This is for all of us designers. This is where we're actually going to see the front end of the product and we should

[14:00] run the backend so that it functions. So, I'm going to go and say start servers in background. So, you're going to type start servers and background. Enter.

[14:18] I just have to So once you save it um you put the env file it's saved. Yeah. It doesn't matter the location or the location. It just you just have to have av file any in your it's there somewhere. It's just a false. Oh, perfect. Okay. So then you're good to go. So now you're going to come in and we're at the stage where you're going to say start servers in

[14:43] background. Okay. So sorry now I'm caught up with some of you guys. We're now going to go open the frontend server. This is LLM Council. Um it's really bad UI. So that's one of the reasons I chose this project. Um Andre Carpathi is a genius, but he's clearly not a designer. So, now that we're here, this is kind of where the fun starts. Um, is we're

[15:12] actually going to make changes. Actually, sorry. Let me let me show you how it works first. I forgot this point. Um, oh, maybe we don't want to. Never mind. I'm not going to I'm going to skip that part. Okay. So, we're now going to make changes to this page directly in the code. So I'm going to come in back here and I am going to say something like

[15:35] you are a worldclass product designer. I want to redesign this page to look like the presentation link. I want you to adhere to the colors, the shapes, and the movement of the presentation. Make sure that you are first planning this out for me. So, when I said I want it to look at the presentation, I'm going to send it this I'm going to send it the presentation

[16:14] you guys are looking at. I actually want to also say that the presentation link just focus on this first page. Okay, I'm going to explain this in a second, but I'm going to start running it because it's going to take a minute. What do I mean here? Okay, a few things. You are a worldclass product engineer. I like to say this to set the

[16:42] stage with my AIS of what they're doing. Um, I actually asked Vyro this question before we got here of like is this still something that people do because I was worried that people don't do this anymore because AI moves so quickly. He told me that because we are designing that it's definitely still it makes sense because Claude code is thinking about code. So when you give it this prompt it's like shifting its mindset I guess you could say and it's trying to think more like a designer. Um, so when I say you're a world-class designer, that's that piece. And then I I quickly came up with this prompt. Um, honestly,

[17:18] I'm sure you guys have looked at prompting and everything. You could go into way more detail. Um, but we're going to just wing it and see what happens with this. The other really important thing to note is this thing I said at the end. Make sure that you are first planning this out for me. Claude Code has a planning mode. a plan mode. This has been a game changer for me because basically what I'm telling it is before you go and do anything, think about it, look at the code and come up with an idea and ask questions so that we can validate together that the plan makes sense. Um, since I

[17:57] started doing planning mode, I have way less back and forth. So, I do this with almost every time I'm I'm prompting cloud code. Um, so basically another thing for you guys is it's clearly asking me a lot of questions. Um, some of some of them I don't know the answers to. Some of them I like to look at and I'm trying to Oh, it's actually I see what it's doing. Um, but it's code. A lot of it's code. And the best way to learn how to prompt better, how to work better with cloud code is to actually start to read this and understand what cloud code is doing. Um, I think it's a

[18:34] really great way to learn more about [laughter]

[18:41] so you can say it. You can say, but also yes, there's the toggle which you can use too. Good question. [clears throat] We have some time. Who has questions? Yes, I will send this to you guys. Yeah. So, you can go through it yourself for sure. Use something else like a random website. Please use whatever you want. Um, this was just this was Oh, sorry. Yes, you

[19:13] don't have to use this presentation. Thank you. Good point. Reference, put whatever prompt you want. Do you want it to look like claw.ai? Um, do you want it to, I don't know, your favorite website? You want it to look like Sesame Street? Whatever you want to do, you can prompt it and see what happens. This is like part of the

[19:34] fun. Um, I'm still in plan mode because I think I gave it too big of a See. Okay, so I'm going to show you guys what plan. Some of you guys have already been here. Plan mode. Do I suggest don't ever just accept plan mode. This is your opportunity to go and chat with Claude Code to make sure that it understands what you want. Um, so I'm not going to go into all the details here, but I I really suggest that you guys look at what it's saying. Um, it's going to modify these files. This is the front-end components it's going to bring in. Um, and then it's telling me it's

[20:13] verification. Um, sometime it's not asking me questions, I think, because of the prompt, but sometimes it asks additional questions that are super enlightening and I'm like, "Oh my gosh, I actually I'm gonna set this well." Um, I'm like, "Oh, I never thought about that idea." Um, this is super interesting. So, I think it's just a way to also understand how Claude Code thinks about things because it's looking at the code base. So, it's also understanding how the platform is being built, which is

[20:40] really cool.

[20:54] Okay, we're gonna keep moving. How many of you guys have a new design? Okay, maybe we'll think that. Um, okay. So, this looks funny. Um, but it did adhere a little bit to my presentation. Um, so if we go back here, this is kind of what the presentation looks like. So, okay. Um, this is one way that you can work within the design, right? You don't even need to go to Figma. You could literally just prompt it. Um, and you can continue to go deeper in this, right? Like you can go on every single detail. You can chat with cloud code and make it what you

[21:36] want. Um, first, so I want to show you Figma, but before I show you how to get it in Figma, there's an important step. It's basically called commit. So what commit means is basically you're saving the file. You're saving a snapshot of your project. I like to commit once you have something that is decent. So, think of it old school when you used to have to save I don't know like your word doc or whatever. It's basically basically the same thing. So, every time you feel like you're making progress and you're at a good point and you want to keep that version, you're going to say you're

[22:13] going to commit. So, you're basically you can just say I want to commit this design or maybe not design this code. I want to commit this code. Enter. And it's going to save the snapshot. So, you have this reference. This took me a while to remember. Like I usually would forget to commit and then I'd go and I'd make all these changes and then I got like I went into it ended up messing up the design and then I wish I could have gone back to that exact point where I felt like it was in a good place. So

[22:45] lesson learned the hallway the hard way. Okay, so all changes look correct. Let me stage and commit. How are we doing? We're we're committing. We're good. Cool. Okay. So, the next step is how many of you guys have set up your Figma MCP? Okay, cool. So, we're going to kind of reverse engineer this is as you guys probably saw Figma now you can take code and bring it into Figma which is really cool. Um, also you can do it the other

[23:26] way which is what's your name? Joseph, you are doing it the other way. You are taking Figma design into the product. So you can do it both ways, but I'm going to show you how to take the design that you came up with and we're actually going to turn it into Figma right now. So what you're going to say, so if you have your Figma MCP open working, hopefully it's working for you guys. Um, you're basically just going to say turn this screen into a

[23:57] enter. And now it should bring your your design directly into Figma.

[24:17] Oh no, my Figma MCP isn't working.

[24:31] Okay, so hopefully some of this worked for you guys. It looks like my Figma MCP is not working.

[24:48] Is it working for you guys? It is. Yay. Did you get it into Figma? Yeah. Let's see. I want to see.

[25:00] Yay. Amazing. Super cool. Yeah, this is the Yeah, perfect. Super cool. Um so yeah this is I think the one I think the one caveat to bringing these file uh to bring it into Figma is it's not necessarily pulling it's not necessarily creating the right tokens and components. Um if your code is set up well it can get there. Um, but so far I found it to be a little tricky. So, it's more of like a, hey, I'm gonna bring it in so I can play with it, but it's not in a final state,

[25:47] if that makes sense.

[26:56] Yeah, I also want to tell you guys, I think some of you guys were bringing in your own Figma designs thinking that you could turn them into code, which you can. Um, that's simple. The reason why I wanted to show you how to take an existing repo is because those of you who work at companies and want to start to implement this, this is more of the process to actually work on top of a codebase that exists today. Um, you still can absolutely take the Figma and put it into that codebase. Um, but this was just a different way to show you

[27:28] guys how to do it. Does that make sense? So when you when you're working on the codebase, um, so let's say your company has their own component library, you're designing in it, they're building in it. What's really cool is you won't need to use, you don't have to use Figma in the same way because if you're using the repo and the codebase, you can say, "Hey, create a welcome screen using the company components." And you could be specific, right? You could say the the primary button, the form field, and it's going to actually create it without you having to go into Figma. It's going to create it because it already has that

[28:09] code and it already knows how to do it. So, it's going to spin it up really quickly. So, that's why I personally think there's going to be less use of Figma. I think where Figma comes into play is when you're working on more complex features. Some of you guys might have different opinions. This is just my own. when you're working on more complex features, that's when I still see the value of Figma a lot. But if you're just trying to make a quick change, I think you don't need Figma to do a quick change overall. Does that answer your

[28:36] question?

[29:06] Okay. How how's everyone doing? You got your file in Figma. We're going to do one last thing now. We're now Oh, I actually don't I don't know if mine actually went into Figma. That's okay. Now, what we're gonna do is we're actually gonna make a change in your Figma and then we're gonna bring it back into code. So, in your Figma file, go change something, fix something, make a design decision that you're going to

[29:38] bring back in. Go ahead. Actually, I'm going to do this really fast. Sorry. I'm going to Let's change this to white. Let's remove here. Okay. This is my new button, right? So now what I'm going to do is I'm going to bring this change back in to code. So I am going to copy this link. I'm I actually just went directly to selection. You could also do the whole thing. Um I'm going to come back and I'm going to say here is my Figma selection for the new conversation button. Apply this new

[30:13] design. I probably would have said it better, but you guys get the idea. Um, I'm going to paste that link and I'm going to hit enter. So now I'm making a change in Figma that's going to be applied to the code. Does that make sense? We're good. Sure. So let's say that you are in you coded something, you brought it into Figma. What's the point of bringing it into Figma? Maybe you want to play with the spacing. Maybe you want to change the you're a designer, right? Maybe you want to rethink something. You want to get into the pixel pushing versus just doing it all in code. Um there's also

[30:53] this whole design system piece which I am not going to touch on yet because that's a whole other beast. Um but well I mean essentially it's this way doesn't work well for components. Like if I I can build a component now out of this. So, I could create the styles, the tokens, and everything. And I could bring it back in to Claude Code. Um, and it'll actually adhere to the tokens and the styling, which is really cool. Um, but why I'm not showing it too much here is because it doesn't actually have anything here yet. So, I would have to like create all that. Um, but there is a lot of really interesting

[31:36] things coming out about design systems and how you can do more with code in design systems, which maybe could be a talk for another time at some point. Um, but essentially why I would want to do this is I just want to play in Figma and I want to get it pixel perfect or I want to try different things and I don't just want to talk to it because I'm a

[31:52] designer. Exactly. Right. Like

[32:10] Okay, let's see. It now says says I lost all my too many screens open. Okay, there we go. You see my button is the new button. It even added a hover state. I didn't ask it to. That's nice.

[32:28] So to kind of wrap things up, you know how we committed. Well, oh, sorry, we're a little this way. There we go. Um, well, now we want to push. What does push mean? Push is when we have committed code and we're ready to take it from our local computer and put it back into the repository so that our whole team gets access to the changes that we've made. Does that make

[32:59] sense? So what we're going to do is we're going to go in and we're basically going to say commit and push. So, a side note is we, if you guys remember, we're building this on an open-source project, which means that we're not necessarily going to be pushing these changes to the open source project. Um, but what we what it is going to do is it's actually going to take our GitHub and it's going to create this project and it's going to push changes in our GitHub. So then we can share to other people that want to see how we

[33:38] designed it.

[33:45] Oh, so see it says push to your own fork. Yes. So it's actually telling me right now it can't do what I said. I it can't push it. So push to own fork. So that's basically means I'm forking the project. I'm taking the project and I'm putting it in my own space. If you guys explore this project further or if you guys want to work on other open-source projects, you can

[34:12] is there my where's my slide? You can contribute a pull request which I'll show you in a second which essentially means that you can create a pull request to the open source and they can see it and then they can accept it or deny it. So you can get your stuff out there. So if there's someone you admire like Andre Karpathy and you want him to see something really cool you've done, you can do a pull request to his open source and he might see it and accept it and make changes

[34:44] which is super cool. Does that make sense? Are you guys still with me? I know it's been a long evening.

[35:07] Okay, I'm going to show you guys this final.

[35:17] So, this is my project in my personal GitHub. there's this contribute button which is what I was saying if you want to open a poll request and send it to the the owner the original of the open source project this is how you can do it which is super cool um but this is basically the end so you guys just built a product congrats that's super exciting how I would love to know how many of you were successful. Can I get a raise of

[35:54] raise of hands when you got it? Okay. I hope you guys got value out of it. Um, even if you didn't get all the way and we will be sending this slide deck and the pres the presentation and the YouTube as well, so you guys could follow along again. Um, but thank you guys so much. All right, let's [clears throat] uh give another round of applause, please. That was

[36:19] awesome. Just like Diane says, this is trial and error. Trial and error, trial and error. The more you tinker with it, the more comfortable you're in it. Of course, there is some of us who are more familiar. Maybe you have an um engineering background, right? So, it's much easier. Some of us who've never touched, right, a tool like this, so it's of course it's different. So, just keep tinkering with it. Keep uh keep

[36:40] doing it. Uh let's move to a Q&A. So, if anyone has any questions, please let us know. Okay, so Beetto has a question. What's up, Beetto? Diane um regarding cursor. Yes. Right. Uh I mean cursor is I guess similar to you know VS code for example I work you know Amazon I use VS code I use Ko I don't know if you're familiar

[37:06] with Kirro. So but you know versus cursor are there any difference is the same or I can just uh I know that Elena just runs in the terminal. So what what are the advantages the differences? Uh your recommendations is cursor is because it's cool is in or you can use anything really. Um great question. Um so I used cursor here today because I think it's the you know the beginning steps where we had to clone and all of that. um that is like that's the easy I found the easiest way to do that if you don't have a coding background is to do it in cursor. So I

[37:49] started on cursor. It was like my training wheels. I now use something called ghosty which I don't know engineers I hear it's like the hip thing to use. Um but that's what everyone tells me. Um but so ghosty of so ghosty. Um but essentially it's a terminal. Okay. Um, so I'm not an expert here, but my answer is I think cursor is great for beginners to understand the files and to under and to easily you don't have to go into code. When you go into terminal,

[38:19] you do have to use code to do things. Um, which is like the next step that you would go in. Um, I don't think there's like a right or wrong. I think I've seen designers use a whole bunch of different tools. Anti-gravity, I know people are using cloud code and anti-gravity now. Um, I was pushed really hard to use just a terminal like ghosty. So that's what I've been doing and I enjoy it because it's just really clean and I feel like I can just do it here and then I can see my designs and running in the local server. So does that answer your

[38:46] question kind of? Okay. Any other questions? Any other questions? And another thing like tools uh like anyone has used versel like Vzero which was originally for prototyping now they've actually moved towards shipping and being able to push into GitHub. So, so all tools are like sort of like trying to trying to compete, right, for for our attention, for our dollars. But um but yeah,

[39:11] anyway, any questions? Any thoughts? Okay, we have a question. You guys tired? Are you guys tired? We have a raffle, so please don't leave. No, I was wondering what other use cases you've found for cursor since you've been using it for a while. like I'm I'm sure you've come up with new and exciting ways to play with it. So, what

[39:36] else have you done with it? Yeah, I'll talk about specifically. Um, so I basically so cursor is really an IED which basically means you're just like running code in AI within it. So, claude code does does that make okay cloud code um is basically like changed my life. Um, so I can do anything in cloud code now. Um, like I built my presentation, you guys, like Oh, sorry. I Oh, no. You guys saw it already. Like I I literally just prompted it and I took designs from Figma and I built a presentation. Um, I do I created a cloud code skill. I don't know if you guys

[40:16] have heard of skills for PRDs. um which is basically a way where it's not just you probably a lot of you guys have done chat GBT and you created like a project and then you created a PRD out of a project where you just give it a bunch of knowledge but the benefit of cloud code is if you're asking it if you're already in a repo and you're asking it to create a PRD it's actually looking at the code base and it's actually able to create a PRD based on all the knowledge that it has of the product that you're using in a way that no one else can. um

[40:49] any I mean honestly you could use cloud code for everyday things. You don't even have to like asking questions, anything you want. So I use it for like pretty much every use case you could think of. Um and that's kind of my go-to these days. Yeah. And and and you saw OpenAI also came up with Codeex which is basically the you know the competitor for cloud code. Uh we have a question over here

[41:14] Cindy. Yeah. Thanks so much. Um, how do you think the relationship uh I guess the working relationship between like PMS, product designers and then software engineers has changed since you've been using such tools?

[41:37] Um, yeah, in my in my opinion um all the roles have kind of like merged. So now PMs can do prototypes which I think is really cool. If any of you guys have your PMs that are like, "Hey, I have this idea for a design." And they're prototyping it. They're basically getting they're feeding you exactly what they're thinking and then you can take it and take it to the next level. So, I think that's been really awesome. Um, I think now designers can code. Literally, we just did it. Um, engineers, I don't know, engineers are still not wanting to design. Maybe a little design, maybe a

[42:06] little PRDS. Um, maybe they still kind of stick to their own lane in my opinion. Um, but I definitely think it's like merging and I definitely think that every my personal opinion is every designer should be up to date and should be learning these tools because I think it's really going to make or break like how product teams function. It's all

[42:25] going to be cross functional in the end. Exactly. Cool. Any other questions? Thank you. Awesome. Thank you. Thank you, Diane. Thank you so much.

---

About this transcript
Read from YouTube's own caption track and laid out by ViewRank AI (https://viewrankai.com).
ViewRank AI finds the videos already beating a creator's own average on Instagram, TikTok and YouTube Shorts, transcribes them from the audio itself in more than 60 languages, and turns what worked into new ideas and scripts.
Free transcript tools, no account needed: https://viewrankai.com/tools
How to read any video this way: https://viewrankai.com/llms.txt