Figma

Out of context: Reply #90

  • Started
  • Last post
  • 90 Responses
  • mg337

    Why use that at all when you can use Claude and go straight to prototyping in a dev environment, build out pages with React components that leverage Material UI kits in Figma, have a complex prototype built in less than an hour - multiple pages if needed - fully responsive, tokenized, and able to be rebuilt in Figma whenever you want full Material components (MUI or Material 3) since it can literally create that once you've built the functional prototype?

    That's what I'm up to lately. I'm writing an article and tutorial to share online soon. I make no claim to have been the one to figure this out, but through posts about other people's tinkering that focuses 100% on just creating designs in Figma from Claude or Make or whatever, I've spent a ton of time with Claude to figure out a for more complex and useful approach.

    It's not for everyone. It's not for the average UX designer who doesn't code, gets intimidate by Terminal, doesn't use VS Code, doesn't understand development, frameworks, can't set up a local host, etc. I'm hoping to make it a bit more accessible to that kind of designer.

    I just wrapped up an 18 month contract this week, looking for a new job, and hoping this kind of thing for me, as a mix of designer, strategist, and technologist, is a big advantage for me. I've been making stuff with BPT and Claude for around 2 years now, from my art applications, to product prototypes for things I'm hoping to get off the ground. I'm finding that the key thing to doing it well is knowing how to prompt like you're writing a functional spec. I used to write those years ago - 90-120 page specs for client sites. I don't know if a lot of UX designers do that these days; it's more of a BA task from my enterprise experience.

    Anyhow, anyone interesting in knowing more about this?

    mg33 7Permalink
    UpvoteDownvote
    Flag
    • Yes? All this seems so wild and untouchable to me.monospaced
    • I'm interested in this, I work in Figma as I'm a control freak and I find it quicker to flow out and test ideas. I use claude a lot as part of research and planslappy
    • Claude is good when you have generic sites/ app designs but with more specific and freestyle design all AI tools struggle so far.NBQ00
    • hardly opened figma since locking in with claude. excited to read your approachBrokenHD
    • Thanks, guys. I've got a lot of work to do on it. I need to fully test the prompts, approach, etc a couple times to ensure it's sound.mg33
    • 100% I’ve been building with Claude dsg for about a month now and have no idea what I’m doing lol I’d love to learn how to integrate figma and then Claude code_niko
    • definitely interestedscruffics
    • Looking forward your tutorial!Salarrue
    • Looks interesting! So far I’ve spent more time adjusting the Claude output than designing from scratch.Chimp
    • So I can use Claude to make a site and not even use figma? How does that work? How do you publish it after Claude makes it?monospaced
    • I've been having frustations with Figma Make, it really struggles with complex data tables, any suggestions?mrAtor
    • Sure, I am interested. Thanks.renderedred
    • Interested yeah!mort_
    • If you can feed your own presets/ design boilerplate/ UI framework into the AI, it gets much easier to control the output. So my approach has been to create myyuekit
    • own grid system, typographic scale, styling and UI components, then use AI to assemble and build on top of these pieces.yuekit
    • Definitely interested! But to me, they're all just tools. As more of a visual person, oftentimes creating the design myself is more efficient than prompting.nocomply
    • I feel like I'm missing out, but I haven't been able to overcome that challenge. Maybe I'm just doing it wrong? I don't know.nocomply
    • @mono - yes, you can do that to a degree. Imagine building a fully functional prototype to share with a dev instead of static Figma screens or, by comparison...mg33
    • Figma prototypes with the vast limitations. You could turn it into an entire site as raw code (without a CMS) and could probably even build a lightweight CMS.mg33
    • nocomply - totally with you there. I like the designing too. But in this context - using Material as the design format - maybe there's a little less design thanmg33
    • there is bringing a vision to life. This might be more application-centric than other kinds of sites. Ex: I'm using this approach to prototype tools I'mmg33
    • building that will use material design. I choose my colors, they're created as tokens, I choose my fonts, Claude uses standard sizing, and I promptmg33
    • around everything i know I need, often writing as though the prompt is a functional spec.mg33
    Show [[ numHiddenNotes ]] more notesAdd Note
    SaveCancel

View thread