UX Spec
Overview
Section titled “Overview”UX Spec is a design-intent inventory generated after delivery phases: visualDirection, fidelity, typed region elements (role/label), layoutPattern, flows, and links to requirement ids. GrowthOS does not generate mockup bitmaps — Figma owns pixels.
It runs as step 4 in Idea Lab and as a standalone hub at /product/ux. Skip it for non-UI projects. Optional: Design in Figma with agent — pair GrowthOS MCP with Figma MCP so hi-fi frames are built and figmaUrl is written back onto each screen.
Today shows screens still missing a Figma link for PM and designer personas.
What you can do here
Section titled “What you can do here”- Review screens, layout patterns, and visual direction before backlog generation.
- Skip UX Spec when the product has no UI.
- Copy the Figma agent prompt or download the prototype-design skill.
- Open linked frames from UX Spec or Today once figmaUrl is set.
When to use
Section titled “When to use”- After approving delivery phases in Idea Lab for a product with UI.
- Anytime from
/product/uxto continue design after the backlog exists. - When a designer needs a brief for hi-fi frames.
Prerequisites
Section titled “Prerequisites”- A PRD with approved delivery phases (Idea Lab) or an existing UX pack.
- For Figma: a gos_ API key plus Figma MCP connected in your coding agent.
Where to find it
Section titled “Where to find it”- Quick Access → UX Spec
- Direct route:
/product/ux - Idea Lab step: UX Spec
Step-by-step
Section titled “Step-by-step”- From Idea Lab, click Approve & continue to UX Spec (or open
/product/ux). - Review visualDirection, fidelity, and each screen’s layoutPattern and typed elements.
- If you need hi-fi: Settings → API Keys & Agents (or the in-panel CTA), connect GrowthOS MCP + Figma MCP, run the prototype-design skill.
- The agent calls get_ux_design_brief, builds frames, and update_ux_screen with figmaUrl.
- Approve & build full backlog, or Skip UX Spec for non-UI work.
What success looks like
Section titled “What success looks like”- Every P0/P1 screen has clear intent; Figma links exist if you ran the design loop.
- Backlog generation was not blocked by an accidental skip on a UI product.
Tips & best practices
Section titled “Tips & best practices”- Prefer get_ux_design_brief over dumping the full spec into the agent.
- Skip is correct for APIs and internal jobs with no screens.
Common mistakes
Section titled “Common mistakes”- Expecting GrowthOS to paint mockups; it stores intent, Figma stores pixels.
- Skipping UX Spec on a UI product and then wondering why design has no inventory.