UX Spec → Figma with an agent
Overview
Section titled “Overview”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 / time / plan
Section titled “Who / time / plan”- 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).
What you can do here
Section titled “What you can do here”- Download the Figma skill from API Keys & Agents.
- Create frames from layout patterns, then store
figmaUrlon screens.
When to use
Section titled “When to use”- UX Spec is approved (not skipped) and you want high-fidelity frames.
Prerequisites
Section titled “Prerequisites”- Approved UX Spec with a screen inventory.
gos_key plus Figma MCP access.
Where to find it
Section titled “Where to find it”/product/ux(UX Spec).- API Keys & Agents → Figma / prototype-design SKILL.md.
Step-by-step
Section titled “Step-by-step”- Approve UX Spec. Confirm screens show visualDirection and layoutPattern.
- Connect GrowthOS MCP and Figma MCP in the same agent.
- Run the prototype-design skill. Build frames from typed elements — do not invent a new IA.
- Write
figmaUrlback onto each GrowthOS screen.
What success looks like
Section titled “What success looks like”- Each UX Spec screen that needed UI has a
figmaUrl.
Tips & best practices
Section titled “Tips & best practices”- Humans still approve the spec; the agent draws frames.
Common mistakes
Section titled “Common mistakes”- Running Figma skill before UX Spec exists.
- Using this during the 15-minute founder-to-Cursor claim demo.