How to Use Figma AI in Your Design Job: One Map, Seven Workflows
Manish Poduval5 min read
- Figma AI
- Figma agent
- Figma Make
- Figma MCP server
- Claude Design
- AI design workflow
Figma Make, the Figma agent, skills and plugins, Claude with the Figma MCP server, Claude Design… there are more AI tools for designers than ever, and most of us still only use one of them, for ideas.
The fix is not more tools. It's knowing which moment of the week each one is for.
1. Five tools, one map
What are you trying to do? Pick one.
Use
Figma MakeThree rough versions in ten minutes, clickable, before anyone opens a ticket.
Use
The Figma agentIt builds with your components and variables, so the result is a real file, not a picture of one.
Use
A skill (or a generative plugin)Write the chore once in plain English, then run it with a slash, forever.
Use
Claude Code + the Figma MCP serverPull the live product into editable frames, change them, send the change back to code.
Use
Claude DesignA short deck or one-pager from your notes and screenshots, in your brand.
2. Put each tool on your week
- 1BriefAgent reads Jira
- 2ExploreFigma Make
- 3BuildFigma agent
- 4ReviewCrit skill
- 5Hand offMCP ⇄ code
- 6ShareClaude Design
3. Seven workflows to steal
Each one uses tools most product teams already have: a design system, Jira, Confluence, Figma and Microsoft 365.
① Jira ticket → three directions in your system
Prompt@Atlassian read DES-142. Make three directions for the empty state using our components and colour variables, one per frame.
② Confluence PRD → every state, not just the happy one
PromptRead the "Refunds v2" page. List every state and edge case it implies, then build each one from the Checkout frame.
③ A design system check you run with a slash
SkillCheck the selection. Flag detached instances, colours not from variables and text not using our styles. Group by screen.
④ Crit comments → tickets, without the copy-paste
PromptGroup the comments on this page by theme. Draft one Jira task per theme in project DES, and show me before you create them.
⑤ The live product → editable frames → back to code
PromptCapture the settings page from localhost:3000 into my Figma file as editable frames.
ThenUpdate the code to match the frame I changed. Use our existing components.
⑥ A prototype real enough to test
PromptMake a working prototype of this flow with our kit. Fake 20 realistic orders so the list scrolls and search works.
⑦ The Friday update, written for you
PromptRead this week's #design-checkout channel in Teams. Write a five-line update for the PM: shipped, blocked, decisions needed.
4. Turn chores into skills
/handoff-check
For the selected frames:
1. Rename layers that still say "Frame 123".
2. List anything not using our variables.
3. Write notes for developers: states, spacing, motion.
4. Draft a Slack message linking the frames. Don't send it.We teach the same habits by hand in Hand off to developers, and you can practise them in our Handoff game.
5. Where AI stops and you start
Give it to AI AI
Keep it
That judgement is what our free unit Your AI design studio is about. If your file needs cleaning first, start with Components and Variables and modes in Learn Figma.
6. Start this week
Want practice first? Every UX challenge comes with ready prompts for Figma Make, Claude and ChatGPT, and a timer. More on where this is all heading in designing with AI and is UI/UX still worth studying in 2026.
Most of this is new. The Figma agent and the MCP server's write-to-canvas are in beta, connectors and skills depend on your plan, and Claude Design launched as a research preview. Check what your plan includes before you roll anything out to the team.