product-design-get-context

Gathers and confirms design briefs before product UI design and prototyping workflows.

634|124|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-get-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-design-get-context
Source: https://github.com/AIDotNet/OpenCowork/tree/main/resources/extensions/product-design/skills/product-design-get-context
Command: npx skills add https://github.com/AIDotNet/OpenCowork --skill product-design-get-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product UI builds often start from vague requests, leading to wasted work on the wrong product, wrong visual style, or wrong level of interactivity. This Skill acts as a mandatory design-brief gate that clarifies or confirms the product, visual source, and interactivity expectations before any ideation, prototyping, or image-to-code work begins.

Core Features & Use Cases

  • Question Mode: Asks targeted questions about what the product should do, which visual source (Figma, screenshot, URL, design system) it should match, and the expected interactivity level when details are missing.
  • Playback Mode: Summarizes an already-supplied brief in a pithy format without re-asking answered questions, then names the next workflow.
  • Hard Boundary Enforcement: Blocks UI implementation, scaffolding, server startup, and file creation until the user confirms the design brief.
  • Use Case: A user asks to redesign a login page. The Skill asks about authentication methods, existing design systems to match, and whether full form states or a static mock are needed, then plays back the confirmed brief before handing off to ideation or prototyping.

Quick Start

Ask the agent to design or prototype a product UI screen, and it will first run this context-gathering step to confirm the design brief with you before building.

Frequently Asked Questions about product-design-get-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a product UI design request with an AI agent?

State what the product or screen should do, provide a visual source such as a Figma file, screenshot, or URL if you have one, and specify the interactivity level. The Skill asks targeted questions for anything missing, then plays back a brief for your confirmation before building.

What is a design brief gate in a product design workflow?

A design brief gate is a mandatory checkpoint that resolves the product purpose, visual reference, and interactivity expectations before ideation or prototyping starts. It prevents building from under-specified requests by requiring user confirmation of the summarized brief.

Can I skip the context questions if I already provided design details?

Yes. When the conversation already contains the product goal, visual source, and interactivity level, the Skill runs in playback mode. It summarizes the brief in a pithy format without re-asking answered questions and names the next workflow.

Why does the design agent refuse to start building my prototype?

The Skill enforces a hard boundary that blocks UI implementation, scaffolding, and file creation while context is missing. Answer the questions about product purpose, visual source, and interactivity, then confirm the played-back brief to proceed.

What interactivity levels can I choose for a UI prototype?

You can choose full interactivity, where all controls and states are completely functional, or static, where controls are minimally interactive for faster delivery. This choice shapes how the subsequent prototype or build workflow implements the design.