product-design-user-context

Load and manage saved product and design references for Product Design workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Product Design work loses continuity when product URLs, Figma files, screenshots, and design-system references must be re-supplied for every task. This Skill persists those references in a local user-context file so future design work starts from the right sources.

Core Features & Use Cases

  • Context Persistence: Saves product URLs, Figma files, screenshots, codebase paths, Storybook docs, tokens, and brand assets to a local user-context.md file.
  • Preflight Loading: Reads saved context via a Python script that returns structured JSON of saved entries and unresolved categories.
  • Guided Onboarding: Walks users through first-time setup, saving references with descriptive filenames and structured metadata.
  • Use Case: A designer saves their product URL, Figma file, and key screenshots once; every later prototype, audit, or critique automatically grounds itself in those saved sources.

Quick Start

Ask the assistant to set up Product Design and save your product URL and Figma file as remembered context.

Frequently Asked Questions about product-design-user-context

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

FAQPage Schema
How do I save product and design references for future design work?

Provide references such as product URLs, Figma files, screenshots, or codebase paths during setup, and they are saved to a local user-context.md file. Screenshots are copied into an assets folder with descriptive filenames for later reuse.

How do I see what Product Design remembers about my product?

Ask what Product Design knows, and the saved user-context.md file is read and summarized. The preflight script returns saved entries and unresolved categories as structured JSON.

Where is the saved Product Design context stored?

Context is stored locally at ~/.open-cowork/state/plugins/product-design/user-context.md, with saved screenshots and reference images in an adjacent assets directory. Nothing is sent to external services.

What happens if no saved context exists yet?

The preflight script reports a missing status, and the workflow continues from the current user prompt. Setup is only triggered when the user asks to configure Product Design or save references.

What should not be saved in Product Design context?

Secrets, credentials, API keys, private tokens, and copied customer data must not be saved. Only durable, non-sensitive product and design references should be persisted.