Figma just closed the last excuse PMs had for not shipping polished UI from AI code.
The loop is now complete. Claude Code generates UI. It goes straight into Figma as editable frames. Designers tweak it. Figma MCP sends it back to Claude Code. The entire design-to-engineering handoff cycle that used to take 2-3 weeks now runs in a single session.
This tells you something about where the real constraint in product development has been. PMs always said the bottleneck was getting designs into code. Figma just proved the actual bottleneck was the opposite direction: getting code into a form designers could touch without starting over.
The implication for AI PMs specifically is that “I need to wait for design” stops being a valid dependency. You can prototype flows in Claude Code, push to Figma, get visual feedback in the same afternoon, and iterate without scheduling a sprint.
What makes this particularly sharp: Figma didn’t build an AI code tool. They built a bridge that makes their existing canvas the canonical source of truth for anything AI generates. Every AI coding tool that produces UI now feeds Figma. That’s the real product decision here.
The design tool became the AI output layer without writing a single line of AI.
"You're my personal Hebrew tutor. Build me a 20-minute lesson for today based on my current level [beginner/intermediate/advanced]. Include: 10 new vocabulary words with context, 1 key grammar concept with 3 examples, and 5 practice sentences I should translate. End with tomorrow's preview."
2. Real Conversation Partner
"Let's have a 10-minute conversation in Hebrew about [topic: weekend plans/work/hobbies]. Start each response in Hebrew, then add English corrections below using this format: '❌ You said X → ✅ Say Y (because Z)'. Adjust your Hebrew complexity to match my responses."
In product management, not everything is straight forward maths, or solvable by AI.
Yet, some PMs still make better decisions most of the time.
How?
That's product sense:
"The ability to find the right solution for the user and business, despite limited and ambiguous information."
I love this definition from @Sid Arora.
You start with the PM process:
1. Take a vague & ambiguous problem statement 2. Create, or clarify the overall goal 3. Identify all users in ecosystem 4. Pick 1-2 users 5. Identify major problems of the user 6. Select the problems to solve 7. Brainstorm for solutions 8. Select the highest ROI solution 9. Build and deploy the solution 10. Measure success / collect feedback
This is the most important part! You want to describe your unicorn candidate-market fit. This is your opportunity to make a bumpy career look like a straight line to a sector of the market.
2. Navigation
The beauty of a website is you can add layers. Add in followup pages to deep dive into your experience. Link them. Add in blog & podcast appearances too.