How Figma’s PMs actually use AI every day | Ezra Mechaber (PM, Figma)
- ID
- 41989
- Status
- summarized
- Published
- 02 Nov 2026, 9:04 PM
- Fetched
- 02 Nov 2026, 10:19 PM
- Provider
- Lenny's Newsletter
- Category
- product-startup
- Original URL
- https://www.lennysnewsletter.com/p/how-figmas-pms-actually-use-ai-every
- Source URL
- https://www.lennysnewsletter.com/feed
Summary
- Score
- 7.0
- Created
- 02 Nov 2026, 10:19 PM
- Tags
- Audience
- developersvibe_codersai_agent_usersstartup_founders
What happened
Figma growth PM Ezra Mechaber describes turning his personal Claude Code setup into "PM OS", a shared repo of 31 skills that 60–70 Figma PMs now use — including a Slack-taming skill he runs six times a day and a bug-bash agent built on Codex. He also demos AutoXP, an agent that runs growth experiments end-to-end with a single human checkpoint, and says it found a large win on its first experiment. The episode is a walkthrough of skills, hooks, private sub-repos, and a FigJam MCP integration, plus a real-time writing assistant built with Jev.
Why it matters
The reusable idea here isn't a tool — it's packaging AI workflows as a versioned repo of named skills that a whole team shares, rather than each person keeping private prompts; that's how 60+ non-engineers at one company got on the same setup. If you run a small team, the decision to make is whether your prompts live in one shared repo with hooks and sub-repos or stay personal, and whether an agent like AutoXP with one human checkpoint is an acceptable gate for experiments you'd otherwise run manually. Note the text gives no numbers for AutoXP's "huge win" or its failure rate, so treat the results claim as unverified.
Discussion angle
What belongs in a shared team skills repo versus individual prompts — and where would you insist on more than one human checkpoint before an agent ships a growth experiment?