Skip to content

UX Spec → Figma with an agent

Idea Lab (or a wave) produces a UX Spec screen inventory: visualDirection, typed elements, layoutPattern. Pair GrowthOS MCP with Figma’s remote MCP and run growthos-prototype-design to build high-fidelity frames and write figmaUrl onto each screen.

Skip this playbook when the wave has no UI. Do not generate Figma frames from a skipped UX Spec.

  • Who: Designer or founder after UX Spec exists
  • Time: After delivery phases; not during the 15-minute Cursor claim
  • Plan: Any plan that can run Idea Lab / UX Spec. Figma MCP is separate (Figma account).
  • Download the Figma skill from API Keys & Agents.
  • Create frames from layout patterns, then store figmaUrl on screens.
  • UX Spec is approved (not skipped) and you want high-fidelity frames.
  • Approved UX Spec with a screen inventory.
  • gos_ key plus Figma MCP access.
  • /product/ux (UX Spec).
  • API Keys & Agents → Figma / prototype-design SKILL.md.
  1. Approve UX Spec. Confirm screens show visualDirection and layoutPattern.
  2. Connect GrowthOS MCP and Figma MCP in the same agent.
  3. Run the prototype-design skill. Build frames from typed elements — do not invent a new IA.
  4. Write figmaUrl back onto each GrowthOS screen.
  • Each UX Spec screen that needed UI has a figmaUrl.
  • Humans still approve the spec; the agent draws frames.
  • Running Figma skill before UX Spec exists.
  • Using this during the 15-minute founder-to-Cursor claim demo.