User Context

User Context stores the product and design references a designer uses often, so future Product Design work starts from the right sources.

Use this skill when the user asks to:

• set up Product Design
• get started with Product Design
• onboard with Product Design
• save product or design sources
• see what Product Design remembers
• update saved product or design context
• remember a Product Design preference
• setup my plugin

Critical Overrides

• Refer to the Plugin router $index before proceeding.
• Follow $critical-overrides.
• Before offering onboarding or saving context for future conversations, confirm that local shell access is available, $CODEX_HOME can be resolved, and $CODEX_HOME/state/plugins/product-design/ exists and is writable or can be created in a writable parent directory. If user-context.md already exists, confirm that it is writable too.
• If any check cannot be completed or fails, persistent context is unavailable. Do not offer saved-context onboarding or claim that new context was saved for future conversations. If the user asks to save something, explain that it can be used in the current conversation but not saved for future conversations.

Saved User Context

If user-context.md exists, use it by default.

Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets to ground Product Design work.

Ideation, prototypes, audits, clones, and critiques should match the saved product context unless the user asks for something different.

When a workflow needs visual grounding, attach or include relevant saved screenshots, reference images, tokens, design language, and component references in ImageGen, ideation, prototype, audit, and critique work.

State File

Saved context lives here: