Profi · Workflow

MCP design → code

Structured Figma context via MCP into code — components and tokens, not PNG archaeology.

Purpose

Profi handoff in 2026 is MCP-shaped: Tabor, Mantlr, Reenbit, and agency playbooks all move structured design context into agents and repos. This workflow assumes a decided frame, a living DS, and Code Connect where it exists — AI interprets intent; it does not invent the product.

Steps

1. **Preconditions** — decided frame (`brief-decide-handoff`), tokens published (`tokens-for-agents`), MCP attached (`figma-mcp-practice`). 2. **Select nodes** — pass selection URLs / node ids, not whole-file dumps. 3. **get_design_context (or equiv)** — agent reads hierarchy, components, variables; refuse screenshot-only paths when MCP is available. 4. **Generate against the repo** — match existing package patterns; run the project’s lint/typecheck. 5. **Review as design+eng** — visual diff + code review; open PR only after both say yes.

When to use / Skip

Use for production-bound UI with a real component library. Skip for throwaway prototypes (`spec-ai-prototype`) or when the Figma file is unstructured — fix structure first. Falsifier: if the PR hard-codes colors that exist as variables, the MCP path failed — re-run with tokens.