figma-mcp-claude-pm-workflow

A workflow and template kit for product managers: using Claude + Figma to produce use case taxonomies that engineering and partner teams can build from

---

When a product team needs to document a set of interaction patterns for a partner or engineering team to implement, the inputs are rarely in one place. Prototypes live in Figma. Behavioral specs live in documents. Research findings live somewhere else. A whiteboard session can convey the concept, but the implementation-relevant detail — the specific mechanics of each use case, the edge cases, the distinctions that matter for scoping — doesn't survive a whiteboard session reliably.

Manual review of 15+ Figma frames across multiple projects is slow and produces inconsistent output, particularly when a consistent use case schema needs to be applied across all of them.

This workflow addresses that by using Claude Code with the Figma MCP server to systematically extract use cases from prototype frames — applying a consistent schema, flagging edge cases, and writing findings to a structured output file — and then using Claude.ai to synthesize across that output and any additional source material into a final taxonomy.

The specific use case this was built for: documenting interaction patterns that were working in one conversational channel so that a partner team could build equivalent functionality in a second channel. The workflow is general enough to apply to other cross-team documentation efforts with similar characteristics.

---

Good fit:

• You have 10 or more Figma frames to analyze, particularly across multiple projects
• The output will be used by a partner team or engineering team for scoping and requirements breakdown — not just for internal team alignment
• Your source material is fragmented across prototypes, specs, and research, and you need synthesis across all of them