Figma — what creators actually do with it

In these 8 posts Figma mostly sits at one end of an AI coding loop rather than being the main design tool. @designteamofone lets Claude Code build the first version from one prompt, sends pages to Figma to explore ideas like hover states and an ASCII footer, then uses the MCP server to push the result back to code, arguing the canvas keeps room for experimentation code to canvas and back. @nateherkai connects Figma MCP and Playwright (each paired in 2 posts) alongside the Impeccable skill (also 2) so Claude can design, build and screenshot-test a site design stack, repeated in an earlier version.

On cost and doubts: @artificial.isabel says she assumed "the figma people were scamming" until a meta prompt worked, and that it burned through her Claude Pro weekly credits meta prompt. @raycfu shows Figma Make turning a pasted product requirements doc into a clickable prototype that uses design-system components, and generating four versions of a screen side by side Figma Make tips. That post and @designteamofone's both carry #FigmaPartner, so treat them as sponsored.

Some tags are about competition or are thin. @tenfoldmarc's post is really about Google Stitch, with Figma named only in the unverified claim that Stitch dropped Figma's stock 12% in a day Stitch MCP. @gregisenberg's six-step process for avoiding "AI slop" apps tags Figma, but the visible steps center on Google AI Studio, Claude and Flux polished AI apps, and @neuwebstudio's animation pack is a comment-gated freebie animation pack.

It fits designers who want to keep a visual canvas while an agent writes the code. The archive-trained taste guide covers the taste side of that workflow.